0s autopkgtest [03:35:47]: starting date and time: 2025-02-16 03:35:47+0000 0s autopkgtest [03:35:47]: git checkout: 325255d2 Merge branch 'pin-any-arch' into 'ubuntu/production' 0s autopkgtest [03:35:47]: host juju-7f2275-prod-proposed-migration-environment-20; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.y232t2kn/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 autopkgtest-ppc64el --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-20@bos03-ppc64el-29.secgroup --name adt-plucky-ppc64el-libfprint-20250216-033546-juju-7f2275-prod-proposed-migration-environment-20-2062f309-c473-4bde-a4f4-8ee13d9fd596 --image adt/ubuntu-plucky-ppc64el-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-20 --net-id=net_prod-proposed-migration-ppc64el -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/ 80s autopkgtest [03:37:07]: testbed dpkg architecture: ppc64el 81s autopkgtest [03:37:08]: testbed apt version: 2.9.28 81s autopkgtest [03:37:08]: @@@@@@@@@@@@@@@@@@@@ test bed setup 81s autopkgtest [03:37:08]: testbed release detected to be: None 82s autopkgtest [03:37:09]: updating testbed package index (apt update) 82s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [110 kB] 82s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 82s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 82s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 83s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [13.1 kB] 83s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [3120 B] 83s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [810 kB] 83s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [73.0 kB] 83s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main ppc64el Packages [167 kB] 83s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted ppc64el Packages [760 B] 83s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe ppc64el Packages [902 kB] 83s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse ppc64el Packages [4228 B] 83s Fetched 2084 kB in 1s (2050 kB/s) 84s Reading package lists... 84s Reading package lists... 85s Building dependency tree... 85s Reading state information... 85s Calculating upgrade... 85s The following packages will be upgraded: 85s dash gcc-14-base libatomic1 libgcc-s1 libp11-kit0 libstdc++6 libtasn1-6 85s libxdmcp6 85s 8 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 85s Need to get 1476 kB of archives. 85s After this operation, 15.4 kB of additional disk space will be used. 85s Get:1 http://ftpmaster.internal/ubuntu plucky/main ppc64el dash ppc64el 0.5.12-12ubuntu1 [114 kB] 85s Get:2 http://ftpmaster.internal/ubuntu plucky/main ppc64el libatomic1 ppc64el 14.2.0-17ubuntu1 [10.7 kB] 85s Get:3 http://ftpmaster.internal/ubuntu plucky/main ppc64el gcc-14-base ppc64el 14.2.0-17ubuntu1 [53.6 kB] 85s Get:4 http://ftpmaster.internal/ubuntu plucky/main ppc64el libstdc++6 ppc64el 14.2.0-17ubuntu1 [886 kB] 85s Get:5 http://ftpmaster.internal/ubuntu plucky/main ppc64el libgcc-s1 ppc64el 14.2.0-17ubuntu1 [39.2 kB] 85s Get:6 http://ftpmaster.internal/ubuntu plucky/main ppc64el libp11-kit0 ppc64el 0.25.5-2ubuntu2 [305 kB] 85s Get:7 http://ftpmaster.internal/ubuntu plucky/main ppc64el libtasn1-6 ppc64el 4.20.0-2 [55.9 kB] 85s Get:8 http://ftpmaster.internal/ubuntu plucky/main ppc64el libxdmcp6 ppc64el 1:1.1.5-1 [11.6 kB] 86s Preconfiguring packages ... 86s Fetched 1476 kB in 1s (2384 kB/s) 86s (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 ... 106311 files and directories currently installed.) 86s Preparing to unpack .../dash_0.5.12-12ubuntu1_ppc64el.deb ... 86s Unpacking dash (0.5.12-12ubuntu1) over (0.5.12-9ubuntu1) ... 86s Setting up dash (0.5.12-12ubuntu1) ... 86s (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 ... 106311 files and directories currently installed.) 86s Preparing to unpack .../libatomic1_14.2.0-17ubuntu1_ppc64el.deb ... 86s Unpacking libatomic1:ppc64el (14.2.0-17ubuntu1) over (14.2.0-16ubuntu1) ... 86s Preparing to unpack .../gcc-14-base_14.2.0-17ubuntu1_ppc64el.deb ... 86s Unpacking gcc-14-base:ppc64el (14.2.0-17ubuntu1) over (14.2.0-16ubuntu1) ... 86s Setting up gcc-14-base:ppc64el (14.2.0-17ubuntu1) ... 86s (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 ... 106311 files and directories currently installed.) 86s Preparing to unpack .../libstdc++6_14.2.0-17ubuntu1_ppc64el.deb ... 86s Unpacking libstdc++6:ppc64el (14.2.0-17ubuntu1) over (14.2.0-16ubuntu1) ... 86s Setting up libstdc++6:ppc64el (14.2.0-17ubuntu1) ... 86s (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 ... 106311 files and directories currently installed.) 86s Preparing to unpack .../libgcc-s1_14.2.0-17ubuntu1_ppc64el.deb ... 86s Unpacking libgcc-s1:ppc64el (14.2.0-17ubuntu1) over (14.2.0-16ubuntu1) ... 86s Setting up libgcc-s1:ppc64el (14.2.0-17ubuntu1) ... 87s (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 ... 106311 files and directories currently installed.) 87s Preparing to unpack .../libp11-kit0_0.25.5-2ubuntu2_ppc64el.deb ... 87s Unpacking libp11-kit0:ppc64el (0.25.5-2ubuntu2) over (0.25.5-2ubuntu1) ... 87s Preparing to unpack .../libtasn1-6_4.20.0-2_ppc64el.deb ... 87s Unpacking libtasn1-6:ppc64el (4.20.0-2) over (4.19.0-3build1) ... 87s Preparing to unpack .../libxdmcp6_1%3a1.1.5-1_ppc64el.deb ... 87s Unpacking libxdmcp6:ppc64el (1:1.1.5-1) over (1:1.1.3-0ubuntu6) ... 87s Setting up libxdmcp6:ppc64el (1:1.1.5-1) ... 87s Setting up libp11-kit0:ppc64el (0.25.5-2ubuntu2) ... 87s Setting up libatomic1:ppc64el (14.2.0-17ubuntu1) ... 87s Setting up libtasn1-6:ppc64el (4.20.0-2) ... 87s Processing triggers for libc-bin (2.40-4ubuntu1) ... 87s Processing triggers for man-db (2.13.0-1) ... 87s Processing triggers for debianutils (5.21) ... 88s Reading package lists... 88s Building dependency tree... 88s Reading state information... 88s 0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded. 88s autopkgtest [03:37:15]: upgrading testbed (apt dist-upgrade and autopurge) 88s Reading package lists... 89s Building dependency tree... 89s Reading state information... 89s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 89s Starting 2 pkgProblemResolver with broken count: 0 89s Done 89s Entering ResolveByKeep 90s 90s The following packages will be upgraded: 90s iproute2 libc-bin libc-dev-bin libc6 libc6-dev locales 90s 6 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 90s Need to get 11.7 MB of archives. 90s After this operation, 358 kB of additional disk space will be used. 90s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed/main ppc64el libc-dev-bin ppc64el 2.41-1ubuntu1 [25.3 kB] 90s Get:2 http://ftpmaster.internal/ubuntu plucky-proposed/main ppc64el libc6-dev ppc64el 2.41-1ubuntu1 [2046 kB] 91s Get:3 http://ftpmaster.internal/ubuntu plucky-proposed/main ppc64el locales all 2.41-1ubuntu1 [4246 kB] 91s Get:4 http://ftpmaster.internal/ubuntu plucky-proposed/main ppc64el libc6 ppc64el 2.41-1ubuntu1 [3243 kB] 91s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/main ppc64el libc-bin ppc64el 2.41-1ubuntu1 [742 kB] 91s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/main ppc64el iproute2 ppc64el 6.13.0-1ubuntu1 [1419 kB] 91s Preconfiguring packages ... 91s Fetched 11.7 MB in 1s (13.2 MB/s) 91s (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 ... 106311 files and directories currently installed.) 91s Preparing to unpack .../libc-dev-bin_2.41-1ubuntu1_ppc64el.deb ... 91s Unpacking libc-dev-bin (2.41-1ubuntu1) over (2.40-4ubuntu1) ... 91s Preparing to unpack .../libc6-dev_2.41-1ubuntu1_ppc64el.deb ... 91s Unpacking libc6-dev:ppc64el (2.41-1ubuntu1) over (2.40-4ubuntu1) ... 91s Preparing to unpack .../locales_2.41-1ubuntu1_all.deb ... 91s Unpacking locales (2.41-1ubuntu1) over (2.40-4ubuntu1) ... 92s Preparing to unpack .../libc6_2.41-1ubuntu1_ppc64el.deb ... 92s Checking for services that may need to be restarted... 92s Checking init scripts... 92s Checking for services that may need to be restarted... 92s Checking init scripts... 92s Stopping some services possibly affected by the upgrade (will be restarted later): 92s cron: stopping...done. 92s 92s Unpacking libc6:ppc64el (2.41-1ubuntu1) over (2.40-4ubuntu1) ... 92s Setting up libc6:ppc64el (2.41-1ubuntu1) ... 92s Checking for services that may need to be restarted... 92s Checking init scripts... 92s Restarting services possibly affected by the upgrade: 92s cron: restarting...done. 92s 92s Services restarted successfully. 92s (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 ... 106312 files and directories currently installed.) 92s Preparing to unpack .../libc-bin_2.41-1ubuntu1_ppc64el.deb ... 92s Unpacking libc-bin (2.41-1ubuntu1) over (2.40-4ubuntu1) ... 93s Setting up libc-bin (2.41-1ubuntu1) ... 93s (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 ... 106312 files and directories currently installed.) 93s Preparing to unpack .../iproute2_6.13.0-1ubuntu1_ppc64el.deb ... 93s Unpacking iproute2 (6.13.0-1ubuntu1) over (6.10.0-2ubuntu1) ... 93s Setting up iproute2 (6.13.0-1ubuntu1) ... 93s Setting up locales (2.41-1ubuntu1) ... 93s Installing new version of config file /etc/locale.alias ... 94s Generating locales (this might take a while)... 95s en_US.UTF-8... done 95s Generation complete. 95s Setting up libc-dev-bin (2.41-1ubuntu1) ... 95s Setting up libc6-dev:ppc64el (2.41-1ubuntu1) ... 95s Processing triggers for man-db (2.13.0-1) ... 97s Processing triggers for systemd (257.2-3ubuntu1) ... 98s Reading package lists... 98s Building dependency tree... 98s Reading state information... 98s Starting pkgProblemResolver with broken count: 0 98s Starting 2 pkgProblemResolver with broken count: 0 98s Done 98s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 101s autopkgtest [03:37:28]: testbed running kernel: Linux 6.12.0-15-generic #15-Ubuntu SMP Tue Feb 4 16:32:08 UTC 2025 101s autopkgtest [03:37:28]: @@@@@@@@@@@@@@@@@@@@ apt-source libfprint 106s Get:1 http://ftpmaster.internal/ubuntu plucky/main libfprint 1:1.94.8+tod1-0ubuntu1 (dsc) [2928 B] 106s Get:2 http://ftpmaster.internal/ubuntu plucky/main libfprint 1:1.94.8+tod1-0ubuntu1 (tar) [9278 kB] 106s Get:3 http://ftpmaster.internal/ubuntu plucky/main libfprint 1:1.94.8+tod1-0ubuntu1 (diff) [17.5 kB] 106s gpgv: Signature made Tue Sep 3 05:15:30 2024 UTC 106s gpgv: using RSA key D4C501DA48EB797A081750939449C2F50996635F 106s gpgv: Can't check signature: No public key 106s dpkg-source: warning: cannot verify inline signature for ./libfprint_1.94.8+tod1-0ubuntu1.dsc: no acceptable signature found 107s autopkgtest [03:37:34]: testing package libfprint version 1:1.94.8+tod1-0ubuntu1 108s autopkgtest [03:37:35]: build not needed 110s autopkgtest [03:37:37]: test installed-tests: preparing testbed 110s Reading package lists... 110s Building dependency tree... 110s Reading state information... 110s Starting pkgProblemResolver with broken count: 0 110s Starting 2 pkgProblemResolver with broken count: 0 110s Done 111s The following NEW packages will be installed: 111s fontconfig-config fonts-dejavu-core fonts-dejavu-mono gir1.2-fprint-2.0 111s gir1.2-gusb-1.0 gir1.2-json-1.0 gnome-desktop-testing libcairo2 111s libfontconfig1 libfprint-2-2 libfprint-2-tests libfprint-2-tod1 libgusb2 111s libpixman-1-0 libumockdev0 libxcb-render0 libxcb-shm0 libxrender1 111s python3-cairo umockdev 111s 0 upgraded, 20 newly installed, 0 to remove and 0 not upgraded. 111s Need to get 10.0 MB of archives. 111s After this operation, 35.7 MB of additional disk space will be used. 111s Get:1 http://ftpmaster.internal/ubuntu plucky/main ppc64el fonts-dejavu-mono all 2.37-8 [502 kB] 111s Get:2 http://ftpmaster.internal/ubuntu plucky/main ppc64el fonts-dejavu-core all 2.37-8 [835 kB] 111s Get:3 http://ftpmaster.internal/ubuntu plucky/main ppc64el fontconfig-config ppc64el 2.15.0-1.1ubuntu2 [37.4 kB] 111s Get:4 http://ftpmaster.internal/ubuntu plucky/main ppc64el gir1.2-json-1.0 ppc64el 1.10.6+ds-1 [10.0 kB] 111s Get:5 http://ftpmaster.internal/ubuntu plucky/main ppc64el libgusb2 ppc64el 0.4.9-1 [43.0 kB] 111s Get:6 http://ftpmaster.internal/ubuntu plucky/main ppc64el gir1.2-gusb-1.0 ppc64el 0.4.9-1 [7460 B] 111s Get:7 http://ftpmaster.internal/ubuntu plucky/main ppc64el libpixman-1-0 ppc64el 0.44.0-3 [334 kB] 111s Get:8 http://ftpmaster.internal/ubuntu plucky/main ppc64el libfprint-2-tod1 ppc64el 1:1.94.8+tod1-0ubuntu1 [70.4 kB] 111s Get:9 http://ftpmaster.internal/ubuntu plucky/main ppc64el libfprint-2-2 ppc64el 1:1.94.8+tod1-0ubuntu1 [306 kB] 111s Get:10 http://ftpmaster.internal/ubuntu plucky/main ppc64el gir1.2-fprint-2.0 ppc64el 1:1.94.8+tod1-0ubuntu1 [7186 B] 111s Get:11 http://ftpmaster.internal/ubuntu plucky/universe ppc64el gnome-desktop-testing ppc64el 2021.1-4 [17.7 kB] 111s Get:12 http://ftpmaster.internal/ubuntu plucky/main ppc64el libfontconfig1 ppc64el 2.15.0-1.1ubuntu2 [190 kB] 111s Get:13 http://ftpmaster.internal/ubuntu plucky/main ppc64el libxcb-render0 ppc64el 1.17.0-2 [17.2 kB] 111s Get:14 http://ftpmaster.internal/ubuntu plucky/main ppc64el libxcb-shm0 ppc64el 1.17.0-2 [5980 B] 111s Get:15 http://ftpmaster.internal/ubuntu plucky/main ppc64el libxrender1 ppc64el 1:0.9.10-1.1build1 [23.1 kB] 111s Get:16 http://ftpmaster.internal/ubuntu plucky/main ppc64el libcairo2 ppc64el 1.18.2-2 [747 kB] 111s Get:17 http://ftpmaster.internal/ubuntu plucky/main ppc64el python3-cairo ppc64el 1.26.1-2build1 [150 kB] 111s Get:18 http://ftpmaster.internal/ubuntu plucky/universe ppc64el libumockdev0 ppc64el 0.19.1-3 [84.6 kB] 111s Get:19 http://ftpmaster.internal/ubuntu plucky/universe ppc64el umockdev ppc64el 0.19.1-3 [84.1 kB] 111s Get:20 http://ftpmaster.internal/ubuntu plucky/universe ppc64el libfprint-2-tests ppc64el 1:1.94.8+tod1-0ubuntu1 [6574 kB] 112s Fetched 10.0 MB in 1s (10.3 MB/s) 112s Selecting previously unselected package fonts-dejavu-mono. 112s (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 ... 106313 files and directories currently installed.) 112s Preparing to unpack .../00-fonts-dejavu-mono_2.37-8_all.deb ... 112s Unpacking fonts-dejavu-mono (2.37-8) ... 112s Selecting previously unselected package fonts-dejavu-core. 112s Preparing to unpack .../01-fonts-dejavu-core_2.37-8_all.deb ... 112s Unpacking fonts-dejavu-core (2.37-8) ... 112s Selecting previously unselected package fontconfig-config. 112s Preparing to unpack .../02-fontconfig-config_2.15.0-1.1ubuntu2_ppc64el.deb ... 112s Unpacking fontconfig-config (2.15.0-1.1ubuntu2) ... 112s Selecting previously unselected package gir1.2-json-1.0:ppc64el. 112s Preparing to unpack .../03-gir1.2-json-1.0_1.10.6+ds-1_ppc64el.deb ... 112s Unpacking gir1.2-json-1.0:ppc64el (1.10.6+ds-1) ... 112s Selecting previously unselected package libgusb2:ppc64el. 112s Preparing to unpack .../04-libgusb2_0.4.9-1_ppc64el.deb ... 112s Unpacking libgusb2:ppc64el (0.4.9-1) ... 112s Selecting previously unselected package gir1.2-gusb-1.0:ppc64el. 112s Preparing to unpack .../05-gir1.2-gusb-1.0_0.4.9-1_ppc64el.deb ... 112s Unpacking gir1.2-gusb-1.0:ppc64el (0.4.9-1) ... 112s Selecting previously unselected package libpixman-1-0:ppc64el. 112s Preparing to unpack .../06-libpixman-1-0_0.44.0-3_ppc64el.deb ... 112s Unpacking libpixman-1-0:ppc64el (0.44.0-3) ... 112s Selecting previously unselected package libfprint-2-tod1:ppc64el. 112s Preparing to unpack .../07-libfprint-2-tod1_1%3a1.94.8+tod1-0ubuntu1_ppc64el.deb ... 112s Unpacking libfprint-2-tod1:ppc64el (1:1.94.8+tod1-0ubuntu1) ... 112s Selecting previously unselected package libfprint-2-2. 112s Preparing to unpack .../08-libfprint-2-2_1%3a1.94.8+tod1-0ubuntu1_ppc64el.deb ... 112s Unpacking libfprint-2-2 (1:1.94.8+tod1-0ubuntu1) ... 112s Selecting previously unselected package gir1.2-fprint-2.0:ppc64el. 112s Preparing to unpack .../09-gir1.2-fprint-2.0_1%3a1.94.8+tod1-0ubuntu1_ppc64el.deb ... 112s Unpacking gir1.2-fprint-2.0:ppc64el (1:1.94.8+tod1-0ubuntu1) ... 112s Selecting previously unselected package gnome-desktop-testing. 112s Preparing to unpack .../10-gnome-desktop-testing_2021.1-4_ppc64el.deb ... 112s Unpacking gnome-desktop-testing (2021.1-4) ... 112s Selecting previously unselected package libfontconfig1:ppc64el. 112s Preparing to unpack .../11-libfontconfig1_2.15.0-1.1ubuntu2_ppc64el.deb ... 112s Unpacking libfontconfig1:ppc64el (2.15.0-1.1ubuntu2) ... 112s Selecting previously unselected package libxcb-render0:ppc64el. 112s Preparing to unpack .../12-libxcb-render0_1.17.0-2_ppc64el.deb ... 112s Unpacking libxcb-render0:ppc64el (1.17.0-2) ... 112s Selecting previously unselected package libxcb-shm0:ppc64el. 112s Preparing to unpack .../13-libxcb-shm0_1.17.0-2_ppc64el.deb ... 112s Unpacking libxcb-shm0:ppc64el (1.17.0-2) ... 112s Selecting previously unselected package libxrender1:ppc64el. 112s Preparing to unpack .../14-libxrender1_1%3a0.9.10-1.1build1_ppc64el.deb ... 112s Unpacking libxrender1:ppc64el (1:0.9.10-1.1build1) ... 112s Selecting previously unselected package libcairo2:ppc64el. 112s Preparing to unpack .../15-libcairo2_1.18.2-2_ppc64el.deb ... 112s Unpacking libcairo2:ppc64el (1.18.2-2) ... 112s Selecting previously unselected package python3-cairo. 112s Preparing to unpack .../16-python3-cairo_1.26.1-2build1_ppc64el.deb ... 112s Unpacking python3-cairo (1.26.1-2build1) ... 112s Selecting previously unselected package libumockdev0:ppc64el. 112s Preparing to unpack .../17-libumockdev0_0.19.1-3_ppc64el.deb ... 112s Unpacking libumockdev0:ppc64el (0.19.1-3) ... 112s Selecting previously unselected package umockdev. 112s Preparing to unpack .../18-umockdev_0.19.1-3_ppc64el.deb ... 112s Unpacking umockdev (0.19.1-3) ... 112s Selecting previously unselected package libfprint-2-tests. 112s Preparing to unpack .../19-libfprint-2-tests_1%3a1.94.8+tod1-0ubuntu1_ppc64el.deb ... 112s Unpacking libfprint-2-tests (1:1.94.8+tod1-0ubuntu1) ... 112s Setting up gnome-desktop-testing (2021.1-4) ... 112s Setting up libpixman-1-0:ppc64el (0.44.0-3) ... 112s Setting up libxrender1:ppc64el (1:0.9.10-1.1build1) ... 112s Setting up libxcb-render0:ppc64el (1.17.0-2) ... 112s Setting up libgusb2:ppc64el (0.4.9-1) ... 112s Setting up libfprint-2-tod1:ppc64el (1:1.94.8+tod1-0ubuntu1) ... 112s Setting up libxcb-shm0:ppc64el (1.17.0-2) ... 112s Setting up fonts-dejavu-mono (2.37-8) ... 112s Setting up fonts-dejavu-core (2.37-8) ... 113s Setting up libumockdev0:ppc64el (0.19.1-3) ... 113s Setting up gir1.2-json-1.0:ppc64el (1.10.6+ds-1) ... 113s Setting up libfprint-2-2 (1:1.94.8+tod1-0ubuntu1) ... 121s Setting up umockdev (0.19.1-3) ... 121s Setting up fontconfig-config (2.15.0-1.1ubuntu2) ... 121s Setting up gir1.2-gusb-1.0:ppc64el (0.4.9-1) ... 121s Setting up libfontconfig1:ppc64el (2.15.0-1.1ubuntu2) ... 121s Setting up gir1.2-fprint-2.0:ppc64el (1:1.94.8+tod1-0ubuntu1) ... 121s Setting up libcairo2:ppc64el (1.18.2-2) ... 121s Setting up python3-cairo (1.26.1-2build1) ... 121s Setting up libfprint-2-tests (1:1.94.8+tod1-0ubuntu1) ... 121s Processing triggers for man-db (2.13.0-1) ... 122s Processing triggers for udev (257.2-3ubuntu1) ... 122s Processing triggers for libc-bin (2.41-1ubuntu1) ... 123s autopkgtest [03:37:50]: test installed-tests: gnome-desktop-testing-runner libfprint-2 123s autopkgtest [03:37:50]: test installed-tests: [----------------------- 123s Running test: libfprint-2/driver-elan-cobo.test 123s ** (umockdev-run:3980): DEBUG: 03:37:50.747: umockdev.vala:127: Created udev test bed /tmp/umockdev.I11D22 123s ** (umockdev-run:3980): DEBUG: 03:37:50.747: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10 123s ** (umockdev-run:3980): DEBUG: 03:37:50.749: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb) 123s ** (umockdev-run:3980): DEBUG: 03:37:50.751: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.I11D22/dev/bus/usb/001/045 123s ** (umockdev-run:3980): DEBUG: 03:37:50.751: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 123s ** (umockdev-run:3980): DEBUG: 03:37:50.752: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 123s ** (umockdev-run:3980): DEBUG: 03:37:50.755: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.I11D22/dev/bus/usb/001/001 123s ** (umockdev-run:3980): DEBUG: 03:37:50.755: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 123s ** (umockdev-run:3980): DEBUG: 03:37:50.756: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 123s (process:3984): libfprint-context-DEBUG: 03:37:50.890: Initializing FpContext (libfprint version 1.94.8+tod1) 123s (process:3984): libfprint-tod-DEBUG: 03:37:50.891: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 123s (process:3984): libfprint-context-DEBUG: 03:37:50.893: No driver found for USB device 1D6B:0002 123s (process:3984): libfprint-device-DEBUG: 03:37:50.893: Device reported probe completion 123s (process:3984): libfprint-device-DEBUG: 03:37:50.893: Completing action FPI_DEVICE_ACTION_PROBE in idle! 123s (process:3984): libfprint-device-DEBUG: 03:37:50.893: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.894: 70702487: ../libfprint/drivers/elan.c:908 123s (process:3984): libfprint-image_device-DEBUG: 03:37:50.895: Image device open completed 123s (process:3984): libfprint-device-DEBUG: 03:37:50.895: Device reported open completion 123s (process:3984): libfprint-device-DEBUG: 03:37:50.895: Completing action FPI_DEVICE_ACTION_OPEN in idle! 123s (process:3984): libfprint-device-DEBUG: 03:37:50.895: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 123s (process:3984): libfprint-device-DEBUG: 03:37:50.895: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 123s (process:3984): libfprint-image_device-DEBUG: 03:37:50.895: Activating image device 123s (process:3984): libfprint-image_device-DEBUG: 03:37:50.895: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.895: 70702942: ../libfprint/drivers/elan.c:960 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.895: 70702948: ../libfprint/drivers/elan.c:951 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.895: 70702954: ../libfprint/drivers/elan.c:892 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.895: 70702958: ../libfprint/drivers/elan.c:100 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.895: [elan] ACTIVATE_NUM_STATES entering state 0 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.895: 70702973: ../libfprint/drivers/elan.c:820 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.895: 70703602: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.896: 70703656: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.896: 70703707: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.896: 70704507: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.896: 70704582: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.897: [elan] ACTIVATE_NUM_STATES entering state 1 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.897: 70704704: ../libfprint/drivers/elan.c:820 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.897: FW ver 0x0140 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.897: [elan] ACTIVATE_NUM_STATES entering state 2 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.897: 70704854: ../libfprint/drivers/elan.c:820 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.897: 70705434: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.897: 70705489: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.897: 70705539: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.898: 70706355: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.898: 70706407: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.898: [elan] ACTIVATE_NUM_STATES entering state 3 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.898: 70706526: ../libfprint/drivers/elan.c:820 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.898: sensor dimensions, WxH: 144x64 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.899: [elan] ACTIVATE_NUM_STATES entering state 4 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.899: 70706654: ../libfprint/drivers/elan.c:820 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.899: skipping command 0x40 0x2a for this device (for devices 0x1 but device is 0x0) 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.899: 70706666: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.899: [elan] ACTIVATE_NUM_STATES completed successfully 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.899: 70706676: ../libfprint/drivers/elan.c:881 123s (process:3984): libfprint-image_device-DEBUG: 03:37:50.899: Image device activation completed 123s (process:3984): libfprint-image_device-DEBUG: 03:37:50.899: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.899: 70706696: ../libfprint/drivers/elan.c:960 123s (process:3984): libfprint-image_device-DEBUG: 03:37:50.899: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.899: 70706708: ../libfprint/drivers/elan.c:960 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.899: 70706712: ../libfprint/drivers/elan.c:792 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.899: 70706716: ../libfprint/drivers/elan.c:100 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.899: [elan] CALIBRATE_NUM_STATES entering state 0 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.899: 70706726: ../libfprint/drivers/elan.c:691 123s (process:3984): libfprint-device-DEBUG: 03:37:50.899: Device reported finger status change: FP_FINGER_STATUS_NEEDED 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.899: 70707232: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.899: 70707274: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.899: 70707307: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.900: 70708042: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.900: 70708092: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.900: [elan] CALIBRATE_NUM_STATES entering state 1 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.900: 70708157: ../libfprint/drivers/elan.c:691 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.900: 70708164: ../libfprint/drivers/elan.c:156 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.900: 70708169: ../libfprint/drivers/elan.c:118 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.900: [elan] CALIBRATE_NUM_STATES entering state 2 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.900: 70708184: ../libfprint/drivers/elan.c:691 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.901: 70708670: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.901: 70708709: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.901: 70708742: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.901: 70709276: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.901: 70709285: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.901: [elan] CALIBRATE_NUM_STATES entering state 3 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.901: 70709294: ../libfprint/drivers/elan.c:691 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.901: 70709299: ../libfprint/drivers/elan.c:634 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.901: calibration mean: 8248, bg mean: 7978, delta: 270 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.901: [elan] CALIBRATE_NUM_STATES completed successfully 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.901: 70709316: ../libfprint/drivers/elan.c:776 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.901: 70709321: ../libfprint/drivers/elan.c:620 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.901: 70709325: ../libfprint/drivers/elan.c:100 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.901: [elan] CAPTURE_NUM_STATES entering state 0 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.902: 70709756: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.902: 70709795: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.902: 70709828: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.902: skipping read, not expecting anything 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.902: 70709892: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.902: [elan] CAPTURE_NUM_STATES entering state 1 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.902: 70710510: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.902: 70710546: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.902: 70710552: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.903: 70711072: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.903: 70711110: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.903: [elan] CAPTURE_NUM_STATES entering state 2 123s (process:3984): libfprint-device-DEBUG: 03:37:50.903: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 123s (process:3984): libfprint-image_device-DEBUG: 03:37:50.903: Image device reported finger status: on 123s (process:3984): libfprint-image_device-DEBUG: 03:37:50.903: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.903: 70711253: ../libfprint/drivers/elan.c:960 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.904: 70711723: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.904: 70711762: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.904: 70711791: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.904: 70712309: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.904: 70712354: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.904: [elan] CAPTURE_NUM_STATES entering state 3 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.904: 70712366: ../libfprint/drivers/elan.c:203 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.904: 70712391: ../libfprint/drivers/elan.c:118 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.904: [elan] CAPTURE_NUM_STATES entering state 1 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.905: 70712865: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.905: 70712905: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.905: 70712941: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.905: 70713587: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.906: 70713627: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.906: [elan] CAPTURE_NUM_STATES entering state 2 123s (process:3984): libfprint-image_device-DEBUG: 03:37:50.906: Image device reported finger status: on 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.906: 70714349: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.906: 70714360: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.906: 70714365: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.907: 70715051: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.907: 70715090: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.907: [elan] CAPTURE_NUM_STATES entering state 3 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.907: 70715102: ../libfprint/drivers/elan.c:203 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.907: 70715107: ../libfprint/drivers/elan.c:118 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.907: [elan] CAPTURE_NUM_STATES entering state 1 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.908: 70715691: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.908: 70715729: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.908: 70715760: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.908: 70716346: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.908: 70716362: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.908: [elan] CAPTURE_NUM_STATES entering state 2 123s (process:3984): libfprint-image_device-DEBUG: 03:37:50.908: Image device reported finger status: on 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.909: 70716927: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.909: 70716968: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.909: 70716976: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.909: 70717505: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.909: 70717536: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.909: [elan] CAPTURE_NUM_STATES entering state 3 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.909: 70717588: ../libfprint/drivers/elan.c:203 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.909: 70717595: ../libfprint/drivers/elan.c:118 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.909: [elan] CAPTURE_NUM_STATES entering state 1 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.910: 70718135: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.910: 70718176: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.910: 70718192: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.911: 70718665: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.911: 70718703: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.911: [elan] CAPTURE_NUM_STATES entering state 2 123s (process:3984): libfprint-image_device-DEBUG: 03:37:50.911: Image device reported finger status: on 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.912: 70719702: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.912: 70719726: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.912: 70719765: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.912: 70720302: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.912: 70720318: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.912: [elan] CAPTURE_NUM_STATES entering state 3 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.912: 70720328: ../libfprint/drivers/elan.c:203 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.912: 70720333: ../libfprint/drivers/elan.c:118 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.912: [elan] CAPTURE_NUM_STATES entering state 1 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.913: 70721186: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.913: 70721230: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.913: 70721263: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.914: 70721864: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.914: 70721896: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.914: [elan] CAPTURE_NUM_STATES entering state 2 123s (process:3984): libfprint-image_device-DEBUG: 03:37:50.914: Image device reported finger status: on 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.914: 70722448: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.914: 70722487: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.914: 70722518: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.915: 70723029: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.915: 70723050: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.915: [elan] CAPTURE_NUM_STATES entering state 3 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.915: 70723061: ../libfprint/drivers/elan.c:203 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.915: 70723066: ../libfprint/drivers/elan.c:118 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.915: [elan] CAPTURE_NUM_STATES entering state 1 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.915: 70723606: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.916: 70723645: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.916: 70723661: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.916: 70724184: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.916: 70724196: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.916: [elan] CAPTURE_NUM_STATES entering state 2 123s (process:3984): libfprint-image_device-DEBUG: 03:37:50.916: Image device reported finger status: on 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.917: 70724737: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.917: 70724774: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.917: 70724782: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.917: 70725382: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.917: 70725403: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.917: [elan] CAPTURE_NUM_STATES entering state 3 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.917: 70725415: ../libfprint/drivers/elan.c:203 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.917: 70725432: ../libfprint/drivers/elan.c:118 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.917: [elan] CAPTURE_NUM_STATES entering state 1 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.918: 70725841: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.918: 70725879: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.918: 70725915: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.919: 70727016: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.919: 70727082: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.919: [elan] CAPTURE_NUM_STATES entering state 2 123s (process:3984): libfprint-image_device-DEBUG: 03:37:50.919: Image device reported finger status: on 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.920: 70727626: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.920: 70727672: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.920: 70727681: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.920: 70728290: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.920: 70728327: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.920: [elan] CAPTURE_NUM_STATES entering state 3 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.920: 70728340: ../libfprint/drivers/elan.c:203 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.920: 70728345: ../libfprint/drivers/elan.c:118 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.920: [elan] CAPTURE_NUM_STATES entering state 1 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.921: 70728865: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.921: 70728875: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.921: 70728881: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.921: 70729584: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.921: 70729593: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.921: [elan] CAPTURE_NUM_STATES entering state 2 123s (process:3984): libfprint-image_device-DEBUG: 03:37:50.921: Image device reported finger status: on 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.922: 70730200: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.922: 70730240: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.922: 70730248: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.923: 70730801: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.923: 70730824: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.923: [elan] CAPTURE_NUM_STATES entering state 3 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.923: 70730836: ../libfprint/drivers/elan.c:203 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.923: 70730841: ../libfprint/drivers/elan.c:118 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.923: [elan] CAPTURE_NUM_STATES entering state 1 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.923: 70731299: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.923: 70731340: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.923: 70731356: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.924: 70731879: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.924: 70731887: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.924: [elan] CAPTURE_NUM_STATES entering state 2 123s (process:3984): libfprint-image_device-DEBUG: 03:37:50.924: Image device reported finger status: on 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.924: 70732397: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.924: 70732423: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.924: 70732458: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.925: 70732967: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.925: 70732978: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.925: [elan] CAPTURE_NUM_STATES entering state 3 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.925: 70732987: ../libfprint/drivers/elan.c:203 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.925: 70732992: ../libfprint/drivers/elan.c:118 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.925: [elan] CAPTURE_NUM_STATES entering state 1 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.925: 70733501: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.925: 70733538: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.925: 70733569: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.926: 70734218: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.926: 70734257: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.926: [elan] CAPTURE_NUM_STATES entering state 2 123s (process:3984): libfprint-image_device-DEBUG: 03:37:50.926: Image device reported finger status: on 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.927: 70734797: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.927: 70734808: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.927: 70734813: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.929: 70736693: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.929: 70736740: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.929: [elan] CAPTURE_NUM_STATES entering state 3 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.929: 70736755: ../libfprint/drivers/elan.c:203 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.929: 70736798: ../libfprint/drivers/elan.c:118 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.929: [elan] CAPTURE_NUM_STATES entering state 1 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.929: 70737265: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.929: 70737310: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.929: 70737347: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.930: 70737823: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.930: 70737862: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.930: [elan] CAPTURE_NUM_STATES entering state 2 123s (process:3984): libfprint-image_device-DEBUG: 03:37:50.930: Image device reported finger status: on 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.930: 70738335: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.930: 70738375: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.930: 70738384: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.931: 70738914: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.931: 70738936: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.931: [elan] CAPTURE_NUM_STATES entering state 3 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.931: 70738948: ../libfprint/drivers/elan.c:203 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.931: 70738953: ../libfprint/drivers/elan.c:118 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.931: [elan] CAPTURE_NUM_STATES entering state 1 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.931: 70739415: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.931: 70739467: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.931: 70739482: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.932: 70739990: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.932: 70740025: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.932: [elan] CAPTURE_NUM_STATES entering state 2 123s (process:3984): libfprint-image_device-DEBUG: 03:37:50.932: Image device reported finger status: on 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.932: 70740496: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.932: 70740506: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.932: 70740511: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.933: 70741087: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.933: 70741109: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.933: [elan] CAPTURE_NUM_STATES entering state 3 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.933: 70741160: ../libfprint/drivers/elan.c:203 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.933: 70741167: ../libfprint/drivers/elan.c:118 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.933: [elan] CAPTURE_NUM_STATES entering state 1 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.934: 70741649: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.934: 70741695: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.934: 70741717: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.934: 70742278: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.934: 70742305: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.934: [elan] CAPTURE_NUM_STATES entering state 2 123s (process:3984): libfprint-image_device-DEBUG: 03:37:50.934: Image device reported finger status: on 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.935: 70742922: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.935: 70742932: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.935: 70742937: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.935: 70743504: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.935: 70743546: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.935: [elan] CAPTURE_NUM_STATES entering state 3 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.935: 70743559: ../libfprint/drivers/elan.c:203 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.935: 70743564: ../libfprint/drivers/elan.c:118 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.935: [elan] CAPTURE_NUM_STATES entering state 1 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.936: 70744026: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.936: 70744078: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.936: 70744095: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.936: 70744586: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.937: 70744624: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.937: [elan] CAPTURE_NUM_STATES entering state 2 123s (process:3984): libfprint-image_device-DEBUG: 03:37:50.937: Image device reported finger status: on 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.937: 70745126: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.937: 70745164: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.937: 70745172: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.938: 70745844: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.938: 70745869: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.938: [elan] CAPTURE_NUM_STATES entering state 3 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.938: 70745886: ../libfprint/drivers/elan.c:203 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.938: 70745891: ../libfprint/drivers/elan.c:118 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.938: [elan] CAPTURE_NUM_STATES entering state 1 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.938: 70746517: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.938: 70746530: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.938: 70746535: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.939: 70747230: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.939: 70747268: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.939: [elan] CAPTURE_NUM_STATES entering state 2 123s (process:3984): libfprint-image_device-DEBUG: 03:37:50.939: Image device reported finger status: on 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.940: 70747769: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.940: 70747806: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.940: 70747813: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.940: 70748370: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.940: 70748401: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.940: [elan] CAPTURE_NUM_STATES entering state 3 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.940: 70748413: ../libfprint/drivers/elan.c:203 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.940: 70748442: ../libfprint/drivers/elan.c:118 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.940: [elan] CAPTURE_NUM_STATES entering state 1 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.941: 70748855: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.941: 70748895: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.941: 70748929: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.941: 70749428: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.941: 70749437: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.941: [elan] CAPTURE_NUM_STATES entering state 2 123s (process:3984): libfprint-image_device-DEBUG: 03:37:50.941: Image device reported finger status: on 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.942: 70749898: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.942: 70749965: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.942: 70749974: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.942: 70750475: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.942: 70750497: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.942: [elan] CAPTURE_NUM_STATES entering state 3 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.942: 70750574: ../libfprint/drivers/elan.c:203 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.942: 70750580: ../libfprint/drivers/elan.c:118 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.942: [elan] CAPTURE_NUM_STATES entering state 1 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.943: 70751122: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.943: 70751161: ../libfprint/drivers/elan.c:366 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.943: 70751195: ../libfprint/drivers/elan.c:379 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.943: 70751617: ../libfprint/drivers/elan.c:346 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.944: 70751626: ../libfprint/drivers/elan.c:335 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.944: [elan] CAPTURE_NUM_STATES entering state 2 123s (process:3984): libfprint-SSM-DEBUG: 03:37:50.944: [elan] CAPTURE_NUM_STATES completed successfully 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.944: 70751649: ../libfprint/drivers/elan.c:586 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.944: 70751653: ../libfprint/drivers/elan.c:315 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.944: 70751660: ../libfprint/drivers/elan.c:272 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.945: 70752647: ../libfprint/drivers/elan.c:272 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.945: 70753613: ../libfprint/drivers/elan.c:272 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.946: 70754594: ../libfprint/drivers/elan.c:272 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.947: 70755561: ../libfprint/drivers/elan.c:272 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.948: 70756586: ../libfprint/drivers/elan.c:272 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.950: 70757781: ../libfprint/drivers/elan.c:272 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.951: 70758810: ../libfprint/drivers/elan.c:272 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.952: 70759812: ../libfprint/drivers/elan.c:272 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.953: 70760792: ../libfprint/drivers/elan.c:272 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.954: 70761796: ../libfprint/drivers/elan.c:272 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.955: 70762798: ../libfprint/drivers/elan.c:272 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.956: 70763808: ../libfprint/drivers/elan.c:272 123s (process:3984): libfprint-elan-DEBUG: 03:37:50.957: 70764796: ../libfprint/drivers/elan.c:272 124s (process:3984): libfprint-assembling-DEBUG: 03:37:51.132: calc delta completed in 0.174625 secs 124s (process:3984): libfprint-assembling-DEBUG: 03:37:51.314: calc delta completed in 0.181484 secs 124s (process:3984): libfprint-assembling-DEBUG: 03:37:51.314: errors: 133465 rev: 143589 124s (process:3984): libfprint-assembling-DEBUG: 03:37:51.486: calc delta completed in 0.171743 secs 124s (process:3984): libfprint-assembling-DEBUG: 03:37:51.486: height is 225 124s (process:3984): libfprint-image_device-DEBUG: 03:37:51.487: Image device captured an image 124s (process:3984): libfprint-image_device-DEBUG: 03:37:51.487: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 124s (process:3984): libfprint-elan-DEBUG: 03:37:51.487: 71295089: ../libfprint/drivers/elan.c:960 124s (process:3984): libfprint-device-DEBUG: 03:37:51.488: Device reported finger status change: FP_FINGER_STATUS_PRESENT 124s (process:3984): libfprint-elan-DEBUG: 03:37:51.488: 71296043: ../libfprint/drivers/elan.c:507 124s (process:3984): libfprint-elan-DEBUG: 03:37:51.488: 71296049: ../libfprint/drivers/elan.c:100 124s (process:3984): libfprint-SSM-DEBUG: 03:37:51.488: [elan] STOP_CAPTURE_NUM_STATES entering state 0 124s (process:3984): libfprint-elan-DEBUG: 03:37:51.488: 71296064: ../libfprint/drivers/elan.c:466 124s (process:3984): libfprint-device-DEBUG: 03:37:51.488: Updated temperature model after 0.59 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 124s (process:3984): libfprint-elan-DEBUG: 03:37:51.488: 71296531: ../libfprint/drivers/elan.c:346 124s (process:3984): libfprint-elan-DEBUG: 03:37:51.488: 71296580: ../libfprint/drivers/elan.c:366 124s (process:3984): libfprint-elan-DEBUG: 03:37:51.488: 71296589: ../libfprint/drivers/elan.c:379 124s (process:3984): libfprint-elan-DEBUG: 03:37:51.488: skipping read, not expecting anything 124s (process:3984): libfprint-elan-DEBUG: 03:37:51.488: 71296601: ../libfprint/drivers/elan.c:335 124s (process:3984): libfprint-SSM-DEBUG: 03:37:51.488: [elan] STOP_CAPTURE_NUM_STATES completed successfully 124s (process:3984): libfprint-elan-DEBUG: 03:37:51.488: 71296612: ../libfprint/drivers/elan.c:483 124s (process:3984): libfprint-device-DEBUG: 03:37:51.488: Device reported finger status change: FP_FINGER_STATUS_NONE 124s (process:3984): libfprint-image_device-DEBUG: 03:37:51.489: Image device reported finger status: off 124s (process:3984): libfprint-image_device-DEBUG: 03:37:51.489: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 124s (process:3984): libfprint-elan-DEBUG: 03:37:51.489: 71296637: ../libfprint/drivers/elan.c:960 124s (process:3984): libfprint-image_device-DEBUG: 03:37:51.489: Deactivating image device 124s (process:3984): libfprint-image_device-DEBUG: 03:37:51.489: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 124s (process:3984): libfprint-elan-DEBUG: 03:37:51.489: 71296654: ../libfprint/drivers/elan.c:960 124s (process:3984): libfprint-elan-DEBUG: 03:37:51.489: 71296659: ../libfprint/drivers/elan.c:975 124s (process:3984): libfprint-image_device-DEBUG: 03:37:51.489: Image device deactivation completed 124s (process:3984): libfprint-image_device-DEBUG: 03:37:51.489: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 124s (process:3984): libfprint-elan-DEBUG: 03:37:51.489: 71296678: ../libfprint/drivers/elan.c:960 124s (process:3984): libfprint-image-DEBUG: 03:37:51.506: Minutiae scan completed in 0.019096 secs 124s (process:3984): libfprint-device-DEBUG: 03:37:51.506: Device reported capture completion 124s (process:3984): libfprint-device-DEBUG: 03:37:51.506: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 124s (process:3984): libfprint-device-DEBUG: 03:37:51.506: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 124s (process:3984): libfprint-elan-DEBUG: 03:37:51.507: 71314661: ../libfprint/drivers/elan.c:939 124s (process:3984): libfprint-elan-DEBUG: 03:37:51.507: 71314668: ../libfprint/drivers/elan.c:100 124s (process:3984): libfprint-image_device-DEBUG: 03:37:51.507: Image device close completed 124s (process:3984): libfprint-device-DEBUG: 03:37:51.507: Device reported close completion 124s (process:3984): libfprint-device-DEBUG: 03:37:51.507: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 124s (process:3984): libfprint-device-DEBUG: 03:37:51.507: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 124s ** (umockdev-run:3980): DEBUG: 03:37:51.630: umockdev.vala:154: Removing test bed /tmp/umockdev.I11D22 124s (umockdev-run:3980): GLib-DEBUG: 03:37:51.636: unsetenv() is not thread-safe and should not be used after threads are created 124s Comparing PNGs /tmp/libfprint-umockdev-test-exo40zwd/capture.png and /usr/share/installed-tests/libfprint-2/elan-cobo/capture.png 124s PASS: libfprint-2/driver-elan-cobo.test 124s Running test: libfprint-2/driver-aes2501.test 124s ** (umockdev-run:3993): DEBUG: 03:37:51.697: umockdev.vala:127: Created udev test bed /tmp/umockdev.DEJG22 124s ** (umockdev-run:3993): DEBUG: 03:37:51.697: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10 124s ** (umockdev-run:3993): DEBUG: 03:37:51.698: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb) 124s ** (umockdev-run:3993): DEBUG: 03:37:51.702: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.DEJG22/dev/bus/usb/001/044 124s ** (umockdev-run:3993): DEBUG: 03:37:51.702: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 124s ** (umockdev-run:3993): DEBUG: 03:37:51.703: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 124s ** (umockdev-run:3993): DEBUG: 03:37:51.706: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.DEJG22/dev/bus/usb/001/001 124s ** (umockdev-run:3993): DEBUG: 03:37:51.706: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 124s ** (umockdev-run:3993): DEBUG: 03:37:51.706: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 124s (process:3997): libfprint-context-DEBUG: 03:37:51.798: Initializing FpContext (libfprint version 1.94.8+tod1) 124s (process:3997): libfprint-tod-DEBUG: 03:37:51.798: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 124s (process:3997): libfprint-context-DEBUG: 03:37:51.800: No driver found for USB device 1D6B:0002 124s (process:3997): libfprint-device-DEBUG: 03:37:51.800: Device reported probe completion 124s (process:3997): libfprint-device-DEBUG: 03:37:51.800: Completing action FPI_DEVICE_ACTION_PROBE in idle! 124s (process:3997): libfprint-device-DEBUG: 03:37:51.800: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 124s (process:3997): libfprint-image_device-DEBUG: 03:37:51.802: Image device open completed 124s (process:3997): libfprint-device-DEBUG: 03:37:51.802: Device reported open completion 124s (process:3997): libfprint-device-DEBUG: 03:37:51.802: Completing action FPI_DEVICE_ACTION_OPEN in idle! 124s (process:3997): libfprint-device-DEBUG: 03:37:51.802: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 124s (process:3997): libfprint-device-DEBUG: 03:37:51.802: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 124s (process:3997): libfprint-image_device-DEBUG: 03:37:51.802: Activating image device 124s (process:3997): libfprint-image_device-DEBUG: 03:37:51.802: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 124s (process:3997): libfprint-SSM-DEBUG: 03:37:51.802: [aes2501] ACTIVATE_NUM_STATES entering state 0 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.802: write 38 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.804: all registers written 124s (process:3997): libfprint-SSM-DEBUG: 03:37:51.804: [aes2501] ACTIVATE_NUM_STATES entering state 1 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.804: read data 1 124s (process:3997): libfprint-SSM-DEBUG: 03:37:51.805: [aes2501] ACTIVATE_NUM_STATES entering state 2 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.805: write 7 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.806: all registers written 124s (process:3997): libfprint-SSM-DEBUG: 03:37:51.806: [aes2501] ACTIVATE_NUM_STATES entering state 3 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.806: 71613841: ../libfprint/drivers/aes2501.c:140 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.806: write 1 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.807: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.807: reg 0xaf = 20 124s (process:3997): libfprint-SSM-DEBUG: 03:37:51.807: [aes2501] ACTIVATE_NUM_STATES entering state 5 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.807: write 7 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.808: all registers written 124s (process:3997): libfprint-SSM-DEBUG: 03:37:51.808: [aes2501] ACTIVATE_NUM_STATES entering state 6 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.808: write 16 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.808: all registers written 124s (process:3997): libfprint-SSM-DEBUG: 03:37:51.808: [aes2501] ACTIVATE_NUM_STATES completed successfully 124s (process:3997): libfprint-image_device-DEBUG: 03:37:51.808: Image device activation completed 124s (process:3997): libfprint-image_device-DEBUG: 03:37:51.808: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 124s (process:3997): libfprint-image_device-DEBUG: 03:37:51.808: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 124s (process:3997): libfprint-device-DEBUG: 03:37:51.808: Device reported finger status change: FP_FINGER_STATUS_NEEDED 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.808: 71616428: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.808: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.812: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.812: 71620539: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.812: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.814: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.819: 71626803: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.819: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.820: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.822: 71629772: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.822: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.824: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.824: 71632537: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.824: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.826: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.827: 71635004: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.827: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.829: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.829: 71637358: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.829: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.831: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.832: 71639683: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.832: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.833: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.834: 71641891: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.834: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.836: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.836: 71644448: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.836: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.841: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.841: 71649247: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.841: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.847: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.849: 71657164: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.849: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.851: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.851: 71659414: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.851: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.853: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.854: 71661657: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.854: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.855: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.856: 71663992: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.856: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.858: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.858: 71666509: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.858: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.865: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.865: 71673292: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.865: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.867: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.868: 71675786: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.868: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.869: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.870: 71677884: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.870: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.871: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.872: 71679858: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.872: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.876: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.876: 71684287: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.876: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.878: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.878: 71686291: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.878: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.880: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.880: 71688559: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.880: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.883: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.884: 71691627: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.884: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.885: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.886: 71693975: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.886: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.887: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.888: 71696286: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.888: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.890: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.890: 71698408: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.890: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.895: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.895: 71703465: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.895: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.897: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.897: 71705502: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.897: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.899: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.899: 71707480: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.899: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.901: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.901: 71709574: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.901: write 23 regs 124s (process:3997): libfprint-device-DEBUG: 03:37:51.902: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.903: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.904: 71711696: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.904: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.905: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.906: 71713644: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.906: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.907: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.908: 71715669: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.908: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.909: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.910: 71717878: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.910: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.912: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.912: 71720226: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.912: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.914: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.915: 71722788: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.915: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.916: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.917: 71725081: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.917: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.918: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.919: 71727233: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.919: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.921: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.921: 71729388: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.921: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.923: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.923: 71731539: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.923: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.925: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.925: 71733483: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.925: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.927: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.927: 71735504: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.927: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.929: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.929: 71737487: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.929: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.931: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.931: 71739572: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.931: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.933: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.933: 71741596: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.933: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.935: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.935: 71743580: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.935: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.937: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.938: 71745623: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.938: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.940: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.940: 71748289: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.940: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.942: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.942: 71750400: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.942: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.944: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.944: 71752428: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.944: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.946: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.946: 71754556: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.946: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.948: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.948: 71756545: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.948: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.950: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.950: 71758591: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.950: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.952: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.952: 71760579: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.952: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.954: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.955: 71762684: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.955: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.956: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.957: 71764696: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.957: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.958: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.959: 71766714: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.959: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.960: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.961: 71768707: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.961: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.962: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.963: 71770712: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.963: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.964: all registers written 124s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.965: 71772738: ../libfprint/drivers/aes2501.c:310 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.965: write 23 regs 124s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.966: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.970: 71778148: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.970: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.972: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.972: 71780250: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.972: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.974: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.974: 71782379: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.974: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.976: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.976: 71784555: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.976: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.978: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.979: 71787113: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.979: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.981: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.981: 71789264: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.981: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.983: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.983: 71791590: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.983: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.985: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.986: 71793761: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.986: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.987: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.988: 71795912: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.988: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.990: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.991: 71798658: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.991: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.993: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.993: 71801592: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.993: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.995: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.996: 71804027: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.996: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.998: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:51.998: 71806461: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:51.998: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.000: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.001: 71808631: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.001: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.002: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.003: 71810736: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.003: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.005: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.005: 71813243: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.005: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.007: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.008: 71816039: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.008: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.010: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.010: 71818484: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.010: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.012: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.013: 71820658: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.013: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.014: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.015: 71822711: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.015: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.016: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.017: 71824827: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.017: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.018: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.019: 71827113: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.019: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.020: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.021: 71829157: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.021: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.022: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.023: 71831118: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.023: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.024: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.025: 71833052: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.025: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.026: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.027: 71835092: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.027: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.029: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.029: 71837245: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.029: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.031: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.032: 71839697: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.032: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.033: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.034: 71841757: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.034: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.035: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.036: 71843960: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.036: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.037: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.038: 71846018: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.038: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.039: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.040: 71848028: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.040: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.041: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.042: 71849979: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.042: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.043: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.044: 71851929: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.044: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.045: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.046: 71853884: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.046: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.047: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.048: 71855924: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.048: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.049: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.050: 71857933: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.050: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.051: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.052: 71860006: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.052: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.053: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.054: 71861996: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.054: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.055: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.056: 71863973: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.056: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.057: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.058: 71865912: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.058: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.059: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.060: 71867845: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.060: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.061: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.062: 71869811: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.062: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.063: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.064: 71871820: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.064: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.065: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.066: 71873922: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.066: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.067: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.068: 71875952: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.068: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.069: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.070: 71878000: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.070: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.072: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.072: 71880423: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.072: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.074: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.074: 71882395: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.074: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.076: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.076: 71884530: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.076: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.078: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.078: 71886598: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.078: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.080: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.081: 71888724: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.081: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.082: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.083: 71890738: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.083: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.084: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.085: 71892827: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.085: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.086: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.087: 71895096: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.087: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.089: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.089: 71897576: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.089: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.091: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.092: 71899717: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.092: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.093: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.094: 71901712: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.094: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.095: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.096: 71903831: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.096: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.098: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.098: 71906540: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.098: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.100: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.100: 71908589: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.100: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.102: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.103: 71910634: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.103: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.104: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.105: 71912730: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.105: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.106: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.107: 71914815: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.107: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.108: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.109: 71916850: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.109: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.110: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.111: 71918879: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.111: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.112: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.113: 71920946: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.113: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.114: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.115: 71922993: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.115: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.116: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.117: 71924924: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.117: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.118: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.119: 71926891: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.119: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.120: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.121: 71928897: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.121: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.122: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.123: 71930884: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.123: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.124: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.125: 71932847: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.125: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.126: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.127: 71934830: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.127: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.130: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.131: 71939002: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.131: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.132: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.133: 71940968: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.133: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.134: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.135: 71943106: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.135: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.137: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.137: 71945391: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.137: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.139: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.140: 71947678: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.140: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.141: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.142: 71949731: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.142: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.143: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.144: 71951706: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.144: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.145: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.146: 71953922: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.146: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.148: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.148: 71956243: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.148: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.150: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.150: 71958305: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.150: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.152: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.152: 71960368: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.152: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.154: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.154: 71962423: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.154: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.156: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.156: 71964499: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.156: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.158: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.158: 71966505: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.158: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.160: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.160: 71968524: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.160: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.162: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.162: 71970619: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.163: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.164: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.165: 71972642: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.165: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.166: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.167: 71974706: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.167: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.168: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.169: 71976890: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.169: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.170: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.171: 71978957: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.171: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.172: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.173: 71980992: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.173: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.176: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.176: 71984387: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.176: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.178: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.178: 71986404: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.178: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.180: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.180: 71988408: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.180: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.182: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.182: 71990444: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.182: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.184: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.184: 71992449: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.184: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.186: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.186: 71994408: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.186: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.188: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.188: 71996380: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.188: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.190: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.190: 71998418: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.190: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.192: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.192: 72000505: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.192: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.194: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.194: 72002550: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.194: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.198: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.199: 72007111: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.199: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.200: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.201: 72009005: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.201: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.202: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.203: 72011022: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.203: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.204: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.205: 72013019: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.205: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.206: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.207: 72015123: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.207: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.209: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.209: 72017140: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.209: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.210: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.211: 72019115: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.211: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.212: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.213: 72021035: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.213: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.214: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.219: 72027078: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.219: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.220: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.221: 72029027: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.221: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.222: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.223: 72031125: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.223: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.225: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.225: 72033127: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.225: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.226: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.227: 72035105: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.227: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.228: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.229: 72037091: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.229: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.230: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.231: 72039069: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.231: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.235: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.235: 72043555: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.235: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.237: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.237: 72045477: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.237: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.239: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.239: 72047458: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.239: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.241: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.241: 72049509: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.241: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.243: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.244: 72051702: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.244: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.245: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.246: 72053681: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.246: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.247: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.248: 72055756: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.248: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.249: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.250: 72057750: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.250: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.251: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.252: 72059721: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.252: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.253: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.254: 72061667: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.254: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.255: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.256: 72063630: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.256: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.257: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.257: 72065598: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.257: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.259: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.260: 72067624: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.260: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.261: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.262: 72069778: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.262: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.263: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.264: 72071768: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.264: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.265: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.266: 72073742: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.266: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.267: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.268: 72075713: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.268: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.269: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.270: 72077659: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.270: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.271: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.271: 72079605: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.271: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.273: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.273: 72081536: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.273: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.275: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.275: 72083532: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.275: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.277: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.277: 72085486: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.277: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.279: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.279: 72087463: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.279: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.281: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.281: 72089437: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.281: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.283: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.283: 72091443: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.283: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.285: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.285: 72093504: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.285: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.287: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.287: 72095510: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.287: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.289: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.289: 72097540: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.289: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.291: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.291: 72099533: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.291: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.293: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.293: 72101483: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.293: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.295: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.295: 72103429: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.295: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.297: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.297: 72105368: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.297: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.299: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.299: 72107332: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.299: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.301: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.301: 72109330: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.301: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.303: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.303: 72111440: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.303: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.305: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.305: 72113387: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.305: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.307: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.307: 72115378: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.307: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.309: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.309: 72117315: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.309: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.311: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.311: 72119285: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.311: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.313: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.313: 72121209: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.313: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.315: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.315: 72123179: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.315: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.317: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.317: 72125155: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.317: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.318: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.319: 72127106: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.319: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.320: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.321: 72129031: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.321: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.324: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.324: 72132542: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.324: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.326: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.326: 72134596: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.326: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.330: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.331: 72139084: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.331: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.333: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.334: 72141699: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.334: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.335: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.336: 72143847: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.336: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.337: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.338: 72145952: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.338: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.347: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.348: 72155881: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.348: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.349: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.350: 72158113: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.350: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.351: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.352: 72160148: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.352: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.353: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.354: 72162129: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.354: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.355: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.356: 72164142: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.356: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.357: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.358: 72166093: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.358: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.359: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.360: 72168034: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.360: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.361: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.362: 72170024: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.362: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.363: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.364: 72171987: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.364: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.365: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.366: 72173939: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.366: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.367: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.368: 72175897: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.368: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.369: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.370: 72177882: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.370: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.371: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.372: 72179838: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.372: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.373: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.374: 72181791: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.374: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.375: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.376: 72183743: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.376: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.377: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.378: 72185706: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.378: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.379: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.380: 72187676: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.380: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.381: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.382: 72189627: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.382: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.383: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.383: 72191600: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.383: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.385: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.385: 72193580: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.385: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.387: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.387: 72195532: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.387: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.389: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.389: 72197481: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.389: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.391: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.391: 72199459: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.391: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.393: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.393: 72201415: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.393: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.395: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.395: 72203385: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.395: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.397: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.397: 72205329: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.397: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.399: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.399: 72207304: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.399: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.401: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.401: 72209376: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.401: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.403: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.403: 72211347: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.403: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.405: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.405: 72213296: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.405: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.407: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.407: 72215280: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.407: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.409: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.409: 72217237: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.409: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.411: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.411: 72219235: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.411: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.413: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.413: 72221204: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.413: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.415: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.415: 72223230: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.415: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.417: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.417: 72225215: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.417: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.419: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.419: 72227347: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.419: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.421: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.421: 72229492: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.421: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.423: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.423: 72231458: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.423: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.427: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.428: 72236113: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.428: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.430: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.430: 72238204: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.430: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.432: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.432: 72240159: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.432: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.434: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.434: 72242264: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.434: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.436: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.436: 72244322: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.436: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.438: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.438: 72246288: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.438: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.440: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.440: 72248277: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.440: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.442: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.442: 72250219: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.442: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.444: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.445: 72252691: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.445: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.446: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.447: 72254645: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.447: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.448: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.449: 72256690: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.449: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.450: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.451: 72258826: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.451: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.452: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.453: 72260796: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.453: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.454: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.455: 72262902: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.455: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.456: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.457: 72264878: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.457: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.458: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.459: 72266863: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.459: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.460: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.461: 72268860: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.461: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.462: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.463: 72270810: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.463: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.464: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.465: 72272884: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.465: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.466: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.467: 72274914: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.467: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.468: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.469: 72276886: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.469: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.470: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.471: 72278835: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.471: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.472: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.473: 72280770: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.473: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.474: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.475: 72282838: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.475: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.476: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.477: 72284791: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.477: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.478: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.479: 72286768: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.479: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.480: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.481: 72288784: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.481: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.482: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.483: 72290789: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.483: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.484: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.485: 72292848: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.485: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.486: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.487: 72294811: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.487: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.488: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.489: 72296785: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.489: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.490: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.491: 72298889: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.491: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.492: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.493: 72301030: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.493: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.494: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.495: 72303173: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.495: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.497: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.497: 72305259: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.497: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.499: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.499: 72307298: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.499: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.501: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.501: 72309262: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.501: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.503: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.503: 72311366: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.503: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.505: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.505: 72313357: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.505: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.507: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.507: 72315375: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.507: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.509: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.509: 72317356: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.509: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.511: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.511: 72319449: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.511: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.513: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.513: 72321515: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.513: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.515: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.515: 72323591: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.515: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.517: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.517: 72325529: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.517: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.519: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.519: 72327610: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.520: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.521: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.522: 72329627: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.522: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.523: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.524: 72331671: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.524: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.525: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.526: 72333676: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.526: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.527: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.528: 72335786: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.528: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.529: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.530: 72337807: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.530: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.531: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.532: 72339807: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.532: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.534: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.534: 72342396: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.534: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.536: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.539: 72347082: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.539: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.542: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.543: 72350948: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.543: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.550: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.556: 72363837: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.556: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.557: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.558: 72366034: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.558: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.560: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.560: 72368257: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.560: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.562: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.562: 72370317: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.562: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.564: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.564: 72372303: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.564: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.566: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.566: 72374286: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.566: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.568: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.568: 72376470: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.568: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.570: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.570: 72378535: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.570: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.572: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.573: 72380816: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.573: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.574: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.575: 72382928: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.575: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.576: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.577: 72384956: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.577: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.578: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.579: 72386921: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.579: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.580: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.581: 72388877: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.581: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.582: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.583: 72390860: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.583: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.584: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.585: 72392815: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.585: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.586: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.587: 72394900: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.587: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.588: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.589: 72396857: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.589: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.590: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.591: 72398834: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.591: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.592: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.593: 72400783: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.593: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.594: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.595: 72402912: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.595: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.596: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.597: 72404992: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.597: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.598: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.599: 72406937: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.599: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.600: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.603: 72411118: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.603: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.605: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.605: 72413278: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.605: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.607: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.607: 72415300: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.607: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.609: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.609: 72417404: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.609: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.611: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.611: 72419451: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.611: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.613: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.613: 72421436: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.613: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.615: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.615: 72423409: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.615: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.617: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.617: 72425377: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.617: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.619: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.619: 72427364: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.619: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.621: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.621: 72429327: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.621: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.623: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.623: 72431470: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.623: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.625: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.625: 72433548: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.625: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.627: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.628: 72435660: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.628: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.629: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.630: 72437649: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.630: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.631: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.632: 72439705: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.632: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.633: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.634: 72441851: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.634: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.635: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.636: 72443932: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.636: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.637: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.638: 72446019: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.638: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.639: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.640: 72447998: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.640: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.641: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.642: 72450009: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.642: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.643: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.644: 72452038: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.644: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.645: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.646: 72453990: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.646: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.647: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.648: 72455997: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.648: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.650: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.651: 72458632: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.651: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.652: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.653: 72460868: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.653: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.654: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.655: 72462884: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.655: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.656: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.657: 72465014: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.657: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.658: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.659: 72467061: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.659: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.660: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.661: 72469066: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.661: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.662: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.663: 72471047: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.663: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.664: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.665: 72473020: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.665: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.666: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.667: 72475023: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.667: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.669: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.669: 72477204: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.669: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.671: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.671: 72479322: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.671: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.673: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.673: 72481386: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.673: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.675: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.675: 72483445: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.675: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.677: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.677: 72485386: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.677: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.679: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.679: 72487344: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.679: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.681: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.681: 72489478: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.681: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.683: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.683: 72491591: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.683: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.685: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.686: 72493937: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.686: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.688: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.688: 72496400: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.688: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.690: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.691: 72498684: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.691: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.692: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.693: 72501138: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.693: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.695: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.695: 72503205: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.695: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.697: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.697: 72505146: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.697: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.698: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.699: 72507150: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.699: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.701: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.702: 72510148: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.702: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.704: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.704: 72512199: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.704: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.706: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.706: 72514329: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.706: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.708: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.708: 72516285: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.708: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.710: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.710: 72518230: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.710: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.712: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.712: 72520235: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.712: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.714: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.714: 72522368: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.714: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.716: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.719: 72527178: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.719: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.721: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.723: 72530860: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.723: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.728: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.728: 72536312: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.728: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.730: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.731: 72538805: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.731: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.732: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.733: 72540985: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.733: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.734: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.735: 72543121: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.735: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.737: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.737: 72545191: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.737: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.739: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.739: 72547248: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.739: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.741: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.741: 72549217: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.741: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.743: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.743: 72551270: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.743: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.745: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.745: 72553254: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.745: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.747: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.747: 72555241: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.747: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.749: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.749: 72557229: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.749: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.751: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.751: 72559254: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.751: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.753: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.753: 72561232: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.753: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.755: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.755: 72563300: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.755: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.757: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.757: 72565320: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.757: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.759: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.759: 72567434: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.759: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.761: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.761: 72569393: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.761: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.763: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.763: 72571412: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.763: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.765: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.765: 72573381: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.765: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.767: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.767: 72575342: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.767: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.769: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.769: 72577307: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.769: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.771: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.771: 72579278: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.771: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.773: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.773: 72581396: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.773: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.777: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.778: 72585668: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.778: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.779: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.780: 72588101: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.780: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.785: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.786: 72594418: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.786: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.789: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.789: 72597295: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.789: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.791: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.791: 72599462: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.791: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.793: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.793: 72601432: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.793: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.795: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.795: 72603612: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.796: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.797: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.798: 72605743: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.798: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.799: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.800: 72607906: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.800: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.801: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.802: 72610048: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.802: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.804: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.804: 72612187: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.804: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.806: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.806: 72614169: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.806: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.807: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.808: 72616118: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.808: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.809: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.810: 72618106: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.810: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.811: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.812: 72620039: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.812: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.813: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.814: 72622002: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.814: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.815: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.816: 72624170: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.816: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.818: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.818: 72626241: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.818: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.820: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.821: 72628681: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.821: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.822: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.823: 72630707: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.823: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.824: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.825: 72632706: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.825: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.826: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.827: 72634644: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.827: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.828: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.828: 72636613: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.829: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.830: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.831: 72638802: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.831: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.832: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.833: 72641068: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.833: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.835: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.835: 72643430: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.835: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.837: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.837: 72645543: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.837: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.839: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.839: 72647517: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.839: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.841: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.841: 72649522: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.841: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.843: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.843: 72651517: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.843: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.845: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.845: 72653540: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.845: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.847: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.848: 72655642: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.848: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.849: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.850: 72657659: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.850: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.851: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.852: 72659669: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.852: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.853: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.854: 72661640: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.854: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.855: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.855: 72663596: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.855: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.857: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.858: 72665642: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.858: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.859: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.860: 72667694: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.860: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.861: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.862: 72669716: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.862: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.863: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.864: 72671729: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.864: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.865: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.866: 72674112: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.866: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.871: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.871: 72679235: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.871: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.873: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.874: 72681911: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.874: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.876: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.876: 72684231: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.876: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.878: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.878: 72686560: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.878: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.881: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.882: 72690330: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.882: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.884: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.885: 72692856: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.885: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.886: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.887: 72694961: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.887: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.888: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.889: 72697127: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.889: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.891: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.891: 72699467: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.891: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.893: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.894: 72701628: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.894: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.895: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.896: 72703914: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.896: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.898: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.898: 72706290: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.898: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.900: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.900: 72708369: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.900: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.902: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.903: 72710686: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.903: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.905: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.905: 72713589: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.905: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.907: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.908: 72715957: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.908: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.909: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.910: 72718108: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.910: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.912: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.912: 72720254: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.912: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.914: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.914: 72722285: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.914: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.916: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.916: 72724485: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.916: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.918: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.919: 72726666: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.919: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.920: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.921: 72728809: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.921: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.922: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.923: 72731059: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.923: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.925: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.925: 72733211: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.925: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.927: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.927: 72735489: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.927: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.929: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.930: 72737652: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.930: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.931: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.932: 72740132: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.932: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.934: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.934: 72742410: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.934: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.936: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.937: 72745060: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.937: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.938: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.939: 72747181: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.939: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.941: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.942: 72750352: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.942: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.944: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.945: 72752844: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.945: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.946: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.947: 72755081: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.947: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.949: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.949: 72757264: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.949: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.951: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.952: 72759745: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.952: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.953: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.954: 72761999: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.954: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.956: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.956: 72764443: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.956: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.958: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.958: 72766515: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.958: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.963: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.964: 72771677: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.964: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.965: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.966: 72773768: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.966: write 23 regs 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.967: all registers written 125s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.968: 72775819: ../libfprint/drivers/aes2501.c:310 125s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.968: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.976: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.977: 72784639: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.977: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.978: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.982: 72790133: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.982: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.984: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.985: 72793249: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.985: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.987: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.990: 72798005: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.990: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.992: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.992: 72800469: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.992: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.994: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:52.995: 72803023: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.995: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:52.999: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.002: 72809624: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.002: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.006: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.010: 72817973: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.010: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.012: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.012: 72820275: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.012: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.014: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.015: 72822641: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.015: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.016: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.017: 72824981: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.017: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.019: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.019: 72827245: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.019: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.022: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.023: 72831231: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.023: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.025: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.026: 72833818: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.026: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.029: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.031: 72839416: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.031: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.033: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.039: 72846967: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.039: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.041: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.041: 72849246: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.041: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.043: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.044: 72851771: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.044: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.049: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.049: 72857437: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.049: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.051: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.052: 72859902: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.052: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.054: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.054: 72862564: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.054: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.059: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.060: 72867645: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.060: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.061: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.062: 72869900: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.062: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.064: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.064: 72872232: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.064: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.066: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.066: 72874559: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.066: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.068: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.069: 72877075: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.069: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.071: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.072: 72880316: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.072: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.074: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.075: 72882768: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.075: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.080: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.080: 72888359: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.080: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.082: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.083: 72890683: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.083: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.086: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.086: 72894322: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.086: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.088: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.089: 72896954: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.089: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.091: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.091: 72899354: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.091: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.099: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.100: 72907662: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.100: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.101: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.102: 72910155: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.102: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.104: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.105: 72912702: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.105: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.106: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.107: 72915010: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.107: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.109: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.109: 72917327: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.109: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.111: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.112: 72919653: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.112: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.116: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.119: 72927057: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.119: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.121: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.122: 72930202: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.122: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.124: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.127: 72935407: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.127: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.133: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.133: 72941598: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.133: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.135: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.136: 72944203: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.136: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.138: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.139: 72946704: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.139: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.140: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.141: 72948986: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.141: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.142: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.143: 72951232: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.143: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.145: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.145: 72953520: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.145: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.147: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.148: 72955705: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.148: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.149: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.150: 72957889: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.150: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.151: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.152: 72960162: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.152: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.154: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.154: 72962389: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.154: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.156: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.157: 72964646: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.157: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.158: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.159: 72966790: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.159: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.160: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.161: 72969023: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.161: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.163: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.163: 72971259: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.163: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.165: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.165: 72973511: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.165: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.167: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.168: 72975814: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.168: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.169: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.170: 72978088: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.170: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.172: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.172: 72980457: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.172: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.174: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.174: 72982608: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.174: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.176: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.177: 72984817: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.177: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.178: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.179: 72987075: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.179: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.181: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.181: 72989236: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.181: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.183: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.183: 72991366: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.183: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.185: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.185: 72993598: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.186: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.187: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.188: 72995805: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.188: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.189: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.190: 72997976: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.190: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.192: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.192: 73000199: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.192: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.194: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.194: 73002506: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.194: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.196: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.197: 73004713: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.197: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.198: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.199: 73006921: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.199: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.201: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.201: 73009279: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.201: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.203: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.203: 73011481: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.203: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.205: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.206: 73013667: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.206: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.211: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.212: 73019954: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.212: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.214: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.214: 73022290: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.214: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.216: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.216: 73024483: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.216: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.218: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.219: 73026753: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.219: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.220: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.223: 73031491: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.223: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.225: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.226: 73034026: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.226: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.228: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.228: 73036435: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.228: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.230: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.231: 73038773: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.231: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.232: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.233: 73041292: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.233: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.235: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.236: 73043773: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.236: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.238: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.238: 73046304: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.238: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.240: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.241: 73048798: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.241: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.242: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.243: 73051164: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.243: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.245: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.245: 73053422: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.245: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.247: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.248: 73055913: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.248: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.249: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.250: 73058225: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.250: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.252: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.253: 73060790: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.253: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.255: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.255: 73063384: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.255: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.257: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.258: 73065929: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.258: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.260: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.261: 73068669: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.261: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.262: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.263: 73071260: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.263: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.265: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.266: 73073862: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.266: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.268: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.269: 73076947: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.269: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.271: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.272: 73080609: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.273: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.275: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.276: 73083817: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.276: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.278: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.278: 73086211: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.278: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.280: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.280: 73088468: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.280: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.282: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.282: 73090522: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.282: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.287: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.289: 73096654: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.289: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.291: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.291: 73099383: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.291: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.296: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.297: 73104696: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.297: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.299: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.300: 73107643: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.300: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.303: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.303: 73111420: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.303: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.305: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.306: 73113648: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.306: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.307: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.311: 73119001: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.311: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.312: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.313: 73121167: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.313: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.315: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.316: 73124270: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.316: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.318: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.319: 73127158: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.319: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.321: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.322: 73130028: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.322: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.324: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.325: 73133344: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.325: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.327: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.328: 73135662: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.328: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.329: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.330: 73137695: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.330: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.331: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.332: 73139983: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.332: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.333: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.334: 73142195: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.334: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.336: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.338: 73146123: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.338: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.340: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.340: 73148328: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.340: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.342: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.342: 73150418: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.342: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.344: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.345: 73152710: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.345: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.346: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.347: 73154713: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.347: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.348: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.349: 73156962: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.349: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.350: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.351: 73159127: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.351: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.353: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.354: 73161731: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.354: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.355: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.356: 73164146: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.356: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.358: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.358: 73166565: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.359: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.361: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.362: 73169800: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.362: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.364: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.364: 73172325: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.364: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.366: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.366: 73174438: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.366: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.368: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.369: 73176926: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.369: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.371: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.371: 73179558: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.371: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.373: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.374: 73182088: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.374: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.376: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.376: 73184349: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.376: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.378: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.378: 73186483: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.378: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.380: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.381: 73188678: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.381: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.382: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.383: 73191145: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.383: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.385: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.385: 73193430: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.385: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.387: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.388: 73195774: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.388: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.389: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.390: 73197990: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.390: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.391: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.392: 73200180: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.392: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.394: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.394: 73202397: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.394: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.396: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.397: 73204823: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.397: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.398: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.399: 73206926: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.399: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.400: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.401: 73209006: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.401: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.402: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.403: 73211184: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.403: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.405: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.405: 73213396: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.405: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.407: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.408: 73215802: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.408: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.409: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.410: 73217860: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.410: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.411: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.412: 73219936: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.412: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.414: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.414: 73222253: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.414: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.416: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.416: 73224318: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.416: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.418: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.419: 73226678: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.419: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.420: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.421: 73228821: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.421: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.423: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.423: 73231473: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.423: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.425: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.426: 73234208: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.426: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.432: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.433: 73241265: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.433: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.435: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.435: 73243577: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.435: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.437: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.438: 73246074: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.438: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.440: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.440: 73248317: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.440: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.442: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.443: 73250775: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.443: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.447: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.448: 73255969: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.448: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.449: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.450: 73258002: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.450: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.451: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.452: 73260039: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.452: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.454: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.454: 73262205: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.454: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.456: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.456: 73264573: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.456: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.458: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.459: 73266861: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.459: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.461: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.462: 73269684: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.462: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.463: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.464: 73271796: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.464: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.465: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.466: 73273916: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.466: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.467: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.468: 73276219: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.468: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.470: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.470: 73278412: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.470: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.472: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.472: 73280596: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.472: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.474: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.475: 73282929: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.475: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.476: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.477: 73285190: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.477: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.479: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.479: 73287256: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.479: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.481: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.482: 73289626: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.482: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.483: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.484: 73291737: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.484: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.485: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.486: 73293799: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.486: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.487: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.488: 73295960: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.488: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.490: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.490: 73298605: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.490: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.492: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.493: 73300727: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.493: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.494: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.495: 73302952: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.495: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.496: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.497: 73305005: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.497: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.499: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.499: 73307208: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.499: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.501: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.502: 73309623: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.502: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.503: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.504: 73311858: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.504: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.506: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.506: 73314422: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.506: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.508: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.509: 73316921: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.509: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.510: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.511: 73319111: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.511: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.513: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.513: 73321265: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.513: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.515: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.515: 73323496: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.515: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.517: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.518: 73325798: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.518: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.519: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.520: 73327937: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.520: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.521: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.522: 73330320: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.522: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.524: all registers written 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.525: 73332692: ../libfprint/drivers/aes2501.c:310 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.525: write 23 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.526: all registers written 126s (process:3997): libfprint-device-DEBUG: 03:37:53.527: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 126s (process:3997): libfprint-image_device-DEBUG: 03:37:53.527: Image device reported finger status: on 126s (process:3997): libfprint-image_device-DEBUG: 03:37:53.527: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.527: 73334818: ../libfprint/drivers/aes2501.c:581 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.527: [aes2501] CAPTURE_NUM_STATES entering state 0 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.527: write 26 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.529: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.529: [aes2501] CAPTURE_NUM_STATES entering state 1 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.529: [aes2501] CAPTURE_NUM_STATES entering state 2 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.529: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.530: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.530: [aes2501] CAPTURE_NUM_STATES entering state 3 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.531: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.531: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.532: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.532: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.532: sum=5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.532: ADREFHI is 50 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.532: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.532: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.533: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.533: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.533: sum=8 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.533: ADREFHI is 48 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.533: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.533: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.534: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.534: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.534: sum=19 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.534: ADREFHI is 40 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.535: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.535: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.535: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.535: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.536: sum=60 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.536: ADREFHI is 38 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.536: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.536: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.536: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.536: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.537: sum=123 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.537: ADREFHI is 30 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.537: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.537: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.537: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.537: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.538: sum=226 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.538: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.538: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.538: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.539: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.539: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.539: sum=461 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.539: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.539: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.539: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.540: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.540: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.540: sum=466 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.540: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.540: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.540: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.541: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.541: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.541: sum=465 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.541: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.541: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.541: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.542: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.542: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.543: sum=620 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.543: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.543: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.543: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.543: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.543: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.547: sum=629 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.547: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.547: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.547: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.548: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.548: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.549: sum=615 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.549: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.549: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.549: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.549: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.549: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.551: sum=585 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.551: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.551: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.551: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.552: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.552: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.552: sum=581 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.552: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.552: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.552: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.553: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.553: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.553: sum=418 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.553: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.553: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.553: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.554: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.554: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.555: sum=406 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.555: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.555: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.555: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.559: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.559: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.560: sum=389 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.560: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.560: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.560: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.561: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.561: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.563: sum=388 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.563: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.563: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.563: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.564: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.564: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.565: sum=393 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.565: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.565: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.565: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.565: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.565: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.566: sum=389 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.566: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.566: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.566: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.566: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.566: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.567: sum=379 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.567: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.567: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.567: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.567: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.567: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.568: sum=361 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.568: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.568: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.568: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.568: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.568: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.575: sum=356 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.575: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.575: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.575: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.576: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.576: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.576: sum=193 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.576: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.576: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.576: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.577: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.577: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.578: sum=178 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.578: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.578: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.578: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.578: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.578: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.579: sum=164 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.579: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.579: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.579: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.579: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.579: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.580: sum=157 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.580: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.580: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.580: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.581: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.581: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.581: sum=152 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.581: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.581: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.581: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.582: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.582: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.583: sum=154 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.583: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.583: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.583: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.583: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.583: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.584: sum=157 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.584: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.584: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.584: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.585: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.585: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.586: sum=161 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.586: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.586: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.586: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.586: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.586: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.587: sum=161 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.587: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.587: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.587: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.588: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.588: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.588: sum=161 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.588: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.588: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.588: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.589: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.589: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.590: sum=162 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.590: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.590: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.590: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.590: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.590: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.591: sum=166 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.591: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.591: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.591: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.591: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.591: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.592: sum=143 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.592: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.592: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.592: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.592: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.592: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.593: sum=106 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.593: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.593: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.593: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.594: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.594: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.594: sum=74 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.594: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.594: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.594: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.595: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.595: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.595: sum=51 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.595: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.595: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.595: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.596: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.596: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.596: sum=40 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.596: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.596: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.596: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.597: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.597: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.597: sum=39 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.597: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.597: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.597: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.598: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.598: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.599: sum=19 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.599: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.599: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.599: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.599: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.599: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.600: sum=13 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.600: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.600: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.600: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.600: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.600: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.601: sum=5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.601: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.601: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.601: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.602: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.602: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.602: sum=2 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.602: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.602: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.602: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.604: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.604: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.604: sum=0 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.604: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.604: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.604: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.605: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.605: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.605: sum=0 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.605: ADREFHI is 28 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.605: [aes2501] CAPTURE_NUM_STATES entering state 4 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.605: write 7 regs 126s (process:3997): libfprint-aeslib-DEBUG: 03:37:53.606: all registers written 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.606: [aes2501] CAPTURE_NUM_STATES entering state 5 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.607: sum=0 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.607: ADREFHI is 28 126s (process:3997): libfprint-assembling-DEBUG: 03:37:53.689: calc delta completed in 0.082324 secs 126s (process:3997): libfprint-assembling-DEBUG: 03:37:53.771: calc delta completed in 0.081923 secs 126s (process:3997): libfprint-assembling-DEBUG: 03:37:53.771: errors: 53228 rev: 72653 126s (process:3997): libfprint-assembling-DEBUG: 03:37:53.873: calc delta completed in 0.101901 secs 126s (process:3997): libfprint-assembling-DEBUG: 03:37:53.873: height is 102 126s (process:3997): libfprint-image_device-DEBUG: 03:37:53.874: Image device captured an image 126s (process:3997): libfprint-image_device-DEBUG: 03:37:53.874: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 126s (process:3997): libfprint-device-DEBUG: 03:37:53.874: Device reported finger status change: FP_FINGER_STATUS_PRESENT 126s (process:3997): libfprint-device-DEBUG: 03:37:53.874: Device reported finger status change: FP_FINGER_STATUS_NONE 126s (process:3997): libfprint-image_device-DEBUG: 03:37:53.874: Image device reported finger status: off 126s (process:3997): libfprint-image_device-DEBUG: 03:37:53.874: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 126s (process:3997): libfprint-image_device-DEBUG: 03:37:53.874: Deactivating image device 126s (process:3997): libfprint-image_device-DEBUG: 03:37:53.874: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 126s (process:3997): libfprint-SSM-DEBUG: 03:37:53.874: [aes2501] CAPTURE_NUM_STATES completed successfully 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.874: 73681908: ../libfprint/drivers/aes2501.c:547 126s (process:3997): libfprint-aes2501-DEBUG: 03:37:53.874: 73681913: ../libfprint/drivers/aes2501.c:820 126s (process:3997): libfprint-image_device-DEBUG: 03:37:53.874: Image device deactivation completed 126s (process:3997): libfprint-image_device-DEBUG: 03:37:53.874: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 126s (process:3997): libfprint-image-DEBUG: 03:37:53.879: Minutiae scan completed in 0.005173 secs 126s (process:3997): libfprint-device-DEBUG: 03:37:53.879: Device reported capture completion 126s (process:3997): libfprint-device-DEBUG: 03:37:53.879: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 126s (process:3997): libfprint-device-DEBUG: 03:37:53.879: Updated temperature model after 1.98 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 126s (process:3997): libfprint-image_device-DEBUG: 03:37:53.880: Image device close completed 126s (process:3997): libfprint-device-DEBUG: 03:37:53.880: Device reported close completion 126s (process:3997): libfprint-device-DEBUG: 03:37:53.880: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 126s (process:3997): libfprint-device-DEBUG: 03:37:53.880: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 126s ** (umockdev-run:3993): DEBUG: 03:37:53.943: umockdev.vala:154: Removing test bed /tmp/umockdev.DEJG22 126s (umockdev-run:3993): GLib-DEBUG: 03:37:53.949: unsetenv() is not thread-safe and should not be used after threads are created 126s Comparing PNGs /tmp/libfprint-umockdev-test-xqy68dxe/capture.png and /usr/share/installed-tests/libfprint-2/aes2501/capture.png 126s PASS: libfprint-2/driver-aes2501.test 126s Running test: libfprint-2/fpi-device.test 127s TAP version 14 127s # random seed: R02S6c01d1cbaaf30cc026b3e9f274ac71a6 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-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-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-fake_test_dev-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 16 /driver/initial_features 127s # libfprint-fake_test_dev-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-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-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-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-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-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-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-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-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-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-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-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-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.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s # libfprint-fake_test_dev-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-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-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-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-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-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-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-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-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-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-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-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-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-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-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 127s # 127s # libfprint-fake_test_dev-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.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev-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 27 /driver/cancel 127s # libfprint-fake_test_dev-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-device-DEBUG: Idle cancelling on ongoing operation! 127s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 127s # 127s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 127s # 127s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 127s # 127s # libfprint-fake_test_dev-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-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 28 /driver/critical 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-fake_test_dev-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 41 /driver/features/probe_updates 127s # End of features tests 127s # Start of initial_features tests 127s ok 42 /driver/initial_features/none 127s ok 43 /driver/initial_features/no_capture 127s ok 44 /driver/initial_features/no_verify 127s ok 45 /driver/initial_features/no_identify 127s ok 46 /driver/initial_features/no_storage 127s ok 47 /driver/initial_features/no_list 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-fake_test_dev-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 ok 52 /driver/open/error 127s # End of open tests 127s # Start of close tests 127s # libfprint-fake_test_dev-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-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 53 /driver/close/error 127s # End of close tests 127s # Start of enroll tests 127s # libfprint-fake_test_dev-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-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: 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-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 54 /driver/enroll/error 127s # libfprint-fake_test_dev-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-device-DEBUG: Device reported enroll progress, reported 1881629318 of 1203568914 have been completed 127s # libfprint-device-DEBUG: Device reported enroll progress, reported 1619693568 of 1203568914 have been completed 127s # libfprint-device-DEBUG: Device reported enroll progress, reported 2049273121 of 1203568914 have been completed 127s # libfprint-fake_test_dev-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-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 55 /driver/enroll/progress 127s # libfprint-fake_test_dev-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-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-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 56 /driver/enroll/update_nbis 127s # libfprint-fake_test_dev-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-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 57 /driver/enroll/update_nbis_wrong_device 127s # libfprint-fake_test_dev-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-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 58 /driver/enroll/update_nbis_wrong_driver 127s # libfprint-fake_test_dev-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-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 59 /driver/enroll/update_nbis_missing_feature 127s # Start of error tests 127s # libfprint-fake_test_dev-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-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-fake_test_dev-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 60 /driver/enroll/error/no_print 127s # End of error tests 127s # End of enroll tests 127s # Start of verify tests 127s # libfprint-fake_test_dev-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-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-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 61 /driver/verify/fail 127s # libfprint-fake_test_dev-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-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-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 62 /driver/verify/retry 127s # libfprint-fake_test_dev-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-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 127s # 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-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 63 /driver/verify/error 127s # libfprint-fake_test_dev-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-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 64 /driver/verify/not_supported 127s # libfprint-fake_test_dev-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-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-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 65 /driver/verify/report_no_cb 127s # libfprint-fake_test_dev-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-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-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 66 /driver/verify/not_reported 127s # libfprint-fake_test_dev-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-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-fake_test_dev-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 67 /driver/verify/complete_retry 127s # End of verify tests 127s # Start of identify tests 127s # libfprint-fake_test_dev-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-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.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s # libfprint-fake_test_dev-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_COLD 127s ok 68 /driver/identify/fail 127s # libfprint-fake_test_dev-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-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.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s # libfprint-fake_test_dev-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_COLD 127s ok 69 /driver/identify/retry 127s # libfprint-fake_test_dev-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-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 127s # 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-fake_test_dev-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_COLD 127s ok 70 /driver/identify/error 127s # libfprint-fake_test_dev-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-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_COLD 127s # libfprint-fake_test_dev-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 71 /driver/identify/not_reported 127s # libfprint-fake_test_dev-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-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-fake_test_dev-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 72 /driver/identify/complete_retry 127s # libfprint-fake_test_dev-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-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-fake_test_dev-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 73 /driver/identify/report_no_cb 127s # libfprint-fake_test_dev-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-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 127s # 127s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 127s # 127s # libfprint-fake_test_dev-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.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s # libfprint-fake_test_dev-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 74 /driver/identify/suspend_continues 127s # libfprint-fake_test_dev-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-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 127s # 127s # libfprint-fake_test_dev-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.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s # libfprint-fake_test_dev-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 75 /driver/identify/suspend_succeeds 127s # libfprint-fake_test_dev-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-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 127s # 127s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 127s # 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-fake_test_dev-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 76 /driver/identify/suspend_busy_error 127s # libfprint-fake_test_dev-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-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 77 /driver/identify/suspend_while_idle 127s # libfprint-fake_test_dev-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-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/fpi-device.test 129s # libfprint-device-DEBUG: Updated temperature model after 2.00 seconds, ratio 0.30 -> 0.74, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_HOT 129s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 129s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 129s # 129s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 129s # 129s # libfprint-device-DEBUG: Device reported identify completion 129s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 129s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 129s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 1 -> 1, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 129s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 131s # 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/fpi-device.test 134s # libfprint-device-DEBUG: Updated temperature model after 3.10 seconds, ratio 0.49 -> 0.26, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 134s # 134s # libfprint-device-DEBUG: Device reported close completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.26 -> 0.26, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s ok 78 /driver/identify/warmup_cooldown 134s # slow test /driver/identify/warmup_cooldown executed in 7.30 secs 134s # End of identify tests 134s # Start of capture tests 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 134s # 134s # libfprint-device-DEBUG: Device reported open completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 134s # 134s # libfprint-device-DEBUG: Device reported close completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s ok 79 /driver/capture/not_supported 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 134s # 134s # libfprint-device-DEBUG: Device reported open completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 134s # 134s # libfprint-device-DEBUG: Device reported capture completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 134s # 134s # libfprint-device-DEBUG: Device reported close completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 134s ok 80 /driver/capture/error 134s # End of capture tests 134s # Start of list tests 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 134s # 134s # libfprint-device-DEBUG: Device reported open completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 134s # 134s # libfprint-device-DEBUG: Device reported listing completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 134s # 134s # libfprint-device-DEBUG: Device reported close completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s ok 81 /driver/list/error 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 134s # 134s # libfprint-device-DEBUG: Device reported open completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 134s # 134s # libfprint-device-DEBUG: Device reported close completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s ok 82 /driver/list/no_storage 134s # End of list tests 134s # Start of delete tests 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 134s # 134s # libfprint-device-DEBUG: Device reported open completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 134s # 134s # libfprint-device-DEBUG: Device reported deletion completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 134s # 134s # libfprint-device-DEBUG: Device reported close completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s ok 83 /driver/delete/error 134s # End of delete tests 134s # Start of clear_storage tests 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 134s # 134s # libfprint-device-DEBUG: Device reported open completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 134s # 134s # libfprint-device-DEBUG: Device reported deletion completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 134s # 134s # libfprint-device-DEBUG: Device reported close completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s ok 84 /driver/clear_storage/error 134s # End of clear_storage tests 134s # Start of cancel tests 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 134s # 134s # libfprint-device-DEBUG: Device reported open completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 134s # 134s # libfprint-device-DEBUG: Device reported deletion completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 134s # 134s # libfprint-device-DEBUG: Device reported close completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s ok 85 /driver/cancel/fail 134s # End of cancel tests 134s # Start of get_current_action tests 134s # libfprint-device-DEBUG: Device reported open completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 134s # 134s # libfprint-device-DEBUG: Device reported close completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s ok 86 /driver/get_current_action/open 134s # End of get_current_action tests 134s # Start of get_cancellable tests 134s ok 87 /driver/get_cancellable/error 134s # libfprint-device-DEBUG: Device reported open completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 134s # 134s # libfprint-device-DEBUG: Device reported close completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s ok 88 /driver/get_cancellable/open 134s # Start of open tests 134s # libfprint-device-DEBUG: Device reported open completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 134s # 134s # libfprint-device-DEBUG: Device reported close completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s ok 89 /driver/get_cancellable/open/internal 134s # End of open tests 134s # End of get_cancellable tests 134s # Start of action_is_cancelled tests 134s # libfprint-device-DEBUG: Device reported open completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 134s # 134s # libfprint-device-DEBUG: Device reported close completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s ok 90 /driver/action_is_cancelled/open 134s ok 91 /driver/action_is_cancelled/error 134s # Start of open tests 134s # libfprint-device-DEBUG: Device reported open completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 134s # 134s # libfprint-device-DEBUG: Device reported close completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s ok 92 /driver/action_is_cancelled/open/internal 134s # End of open tests 134s # End of action_is_cancelled tests 134s # Start of complete_action tests 134s # Start of all tests 134s ok 93 /driver/complete_action/all/error 134s # End of all tests 134s # End of complete_action tests 134s # Start of action_error tests 134s ok 94 /driver/action_error/error 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 134s # 134s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_OPEN 134s # libfprint-device-DEBUG: Device reported open completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 134s # 134s # libfprint-device-DEBUG: Device reported open completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 134s # 134s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_ENROLL 134s # libfprint-device-DEBUG: Device reported enroll completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 134s # 134s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_VERIFY 134s # libfprint-device-DEBUG: Device reported verify completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 134s # 134s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 134s # libfprint-device-DEBUG: Device reported identify completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 134s # 134s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CAPTURE 134s # libfprint-device-DEBUG: Device reported capture completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 134s # 134s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_LIST 134s # libfprint-device-DEBUG: Device reported listing completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 134s # 134s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_DELETE 134s # libfprint-device-DEBUG: Device reported deletion completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 134s # 134s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLEAR_STORAGE 134s # libfprint-device-DEBUG: Device reported deletion completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 134s # 134s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLOSE 134s # libfprint-device-DEBUG: Device reported close completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 134s ok 95 /driver/action_error/all 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 134s # 134s # libfprint-device-DEBUG: Device reported open completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 134s # 134s # libfprint-device-DEBUG: Device reported open completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 134s # 134s # libfprint-device-DEBUG: Device reported enroll completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 134s # 134s # libfprint-device-DEBUG: Device reported verify completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 134s # 134s # libfprint-device-DEBUG: Device reported identify completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 134s # 134s # libfprint-device-DEBUG: Device reported capture completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 134s # 134s # libfprint-device-DEBUG: Device reported listing completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 134s # 134s # libfprint-device-DEBUG: Device reported deletion completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 134s # 134s # libfprint-device-DEBUG: Device reported deletion completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 134s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 134s # 134s # libfprint-device-DEBUG: Device reported close completion 134s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 134s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 134s ok 96 /driver/action_error/fail 134s # End of action_error tests 134s # Start of timeout tests 134s ok 97 /driver/timeout/cancelled 134s # End of timeout tests 134s # End of driver tests 134s PASS: libfprint-2/fpi-device.test 134s Running test: libfprint-2/driver-realtek.test 134s ** (umockdev-run:4010): DEBUG: 03:38:01.691: umockdev.vala:127: Created udev test bed /tmp/umockdev.07AG22 134s ** (umockdev-run:4010): DEBUG: 03:38:01.692: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-8 134s ** (umockdev-run:4010): DEBUG: 03:38:01.693: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-8 (subsystem usb) 134s ** (umockdev-run:4010): DEBUG: 03:38:01.697: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.07AG22/dev/bus/usb/001/025 134s ** (umockdev-run:4010): DEBUG: 03:38:01.697: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 134s ** (umockdev-run:4010): DEBUG: 03:38:01.698: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 134s ** (umockdev-run:4010): DEBUG: 03:38:01.702: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.07AG22/dev/bus/usb/001/001 134s ** (umockdev-run:4010): DEBUG: 03:38:01.702: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 134s ** (umockdev-run:4010): DEBUG: 03:38:01.702: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 134s (process:4014): libfprint-context-DEBUG: 03:38:01.795: Initializing FpContext (libfprint version 1.94.8+tod1) 134s (process:4014): libfprint-tod-DEBUG: 03:38:01.796: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 134s (process:4014): libfprint-context-DEBUG: 03:38:01.798: No driver found for USB device 1D6B:0002 134s (process:4014): libfprint-realtek-DEBUG: 03:38:01.798: 81606216: ../libfprint/drivers/realtek/realtek.c:1225 134s (process:4014): libfprint-realtek-DEBUG: 03:38:01.801: Device name: Realtek USB2.0 Finger Print Bridge 134s (process:4014): libfprint-device-DEBUG: 03:38:01.801: Device reported probe completion 134s (process:4014): libfprint-device-DEBUG: 03:38:01.801: Completing action FPI_DEVICE_ACTION_PROBE in idle! 134s (process:4014): libfprint-device-DEBUG: 03:38:01.801: Not updating temperature model, device can run continuously! 134s (process:4014): libfprint-realtek-DEBUG: 03:38:01.802: 81610170: ../libfprint/drivers/realtek/realtek.c:1270 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.802: [realtek] Init entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.803: [realtek] Init entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.803: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.804: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.804: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.804: [realtek] Init entering state 2 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.804: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.805: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.805: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.805: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.806: [realtek] Init completed successfully 134s (process:4014): libfprint-realtek-DEBUG: 03:38:01.806: Init complete! 134s (process:4014): libfprint-device-DEBUG: 03:38:01.806: Device reported open completion 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.806: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-device-DEBUG: 03:38:01.806: Completing action FPI_DEVICE_ACTION_OPEN in idle! 134s (process:4014): libfprint-device-DEBUG: 03:38:01.806: Not updating temperature model, device can run continuously! 134s (process:4014): libfprint-realtek-DEBUG: 03:38:01.806: 81614058: ../libfprint/drivers/realtek/realtek.c:1333 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.806: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.806: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.806: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-realtek-DEBUG: 03:38:01.807: Successfully cleared storage 134s (process:4014): libfprint-device-DEBUG: 03:38:01.807: Device reported deletion completion 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.807: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-device-DEBUG: 03:38:01.807: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 134s (process:4014): libfprint-device-DEBUG: 03:38:01.807: Not updating temperature model, device can run continuously! 134s (process:4014): libfprint-device-DEBUG: 03:38:01.808: Not updating temperature model, device can run continuously! 134s (process:4014): libfprint-realtek-DEBUG: 03:38:01.808: 81615786: ../libfprint/drivers/realtek/realtek.c:1202 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.808: [realtek] Enroll entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.808: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.808: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.809: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.809: [realtek] Enroll entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.809: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.810: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.810: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.810: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.810: [realtek] Enroll entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.810: Device reported finger status change: FP_FINGER_STATUS_NEEDED 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.811: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.811: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.811: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.811: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.812: [realtek] Enroll entering state 3 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.812: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.812: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.812: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.813: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.813: Device reported finger status change: FP_FINGER_STATUS_PRESENT 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.813: [realtek] Enroll entering state 4 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.813: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.814: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.814: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.815: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.815: Device reported finger status change: FP_FINGER_STATUS_NONE 134s (process:4014): libfprint-device-DEBUG: 03:38:01.815: Device reported enroll progress, reported 1 of 8 have been completed 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.815: [realtek] Enroll entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.815: Device reported finger status change: FP_FINGER_STATUS_NEEDED 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.815: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.815: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.816: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.816: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.816: [realtek] Enroll entering state 3 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.816: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.817: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.817: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.817: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.818: Device reported finger status change: FP_FINGER_STATUS_PRESENT 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.818: [realtek] Enroll entering state 4 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.818: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.818: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.819: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.819: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.820: Device reported finger status change: FP_FINGER_STATUS_NONE 134s (process:4014): libfprint-device-DEBUG: 03:38:01.820: Device reported enroll progress, reported 2 of 8 have been completed 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.820: [realtek] Enroll entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.820: Device reported finger status change: FP_FINGER_STATUS_NEEDED 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.820: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.822: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.822: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.822: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.823: [realtek] Enroll entering state 3 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.823: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.823: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.823: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.826: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.827: Device reported finger status change: FP_FINGER_STATUS_PRESENT 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.827: [realtek] Enroll entering state 4 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.827: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.827: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.827: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.828: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.829: Device reported finger status change: FP_FINGER_STATUS_NONE 134s (process:4014): libfprint-device-DEBUG: 03:38:01.829: Device reported enroll progress, reported 3 of 8 have been completed 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.829: [realtek] Enroll entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.829: Device reported finger status change: FP_FINGER_STATUS_NEEDED 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.829: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.829: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.829: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.829: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.830: [realtek] Enroll entering state 3 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.830: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.830: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.830: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.831: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.831: Device reported finger status change: FP_FINGER_STATUS_PRESENT 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.831: [realtek] Enroll entering state 4 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.831: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.831: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.832: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.832: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.833: Device reported finger status change: FP_FINGER_STATUS_NONE 134s (process:4014): libfprint-device-DEBUG: 03:38:01.833: Device reported enroll progress, reported 4 of 8 have been completed 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.833: [realtek] Enroll entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.833: Device reported finger status change: FP_FINGER_STATUS_NEEDED 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.833: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.833: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.833: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.833: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.834: [realtek] Enroll entering state 3 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.834: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.834: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.834: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.835: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.835: Device reported finger status change: FP_FINGER_STATUS_PRESENT 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.835: [realtek] Enroll entering state 4 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.835: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.835: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.836: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.836: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.837: Device reported finger status change: FP_FINGER_STATUS_NONE 134s (process:4014): libfprint-device-DEBUG: 03:38:01.837: Device reported enroll progress, reported 5 of 8 have been completed 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.837: [realtek] Enroll entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.837: Device reported finger status change: FP_FINGER_STATUS_NEEDED 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.837: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.837: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.838: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.838: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.838: [realtek] Enroll entering state 3 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.838: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.838: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.839: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.839: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.840: Device reported finger status change: FP_FINGER_STATUS_PRESENT 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.840: [realtek] Enroll entering state 4 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.840: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.840: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.840: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.841: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.841: Device reported finger status change: FP_FINGER_STATUS_NONE 134s (process:4014): libfprint-device-DEBUG: 03:38:01.841: Device reported enroll progress, reported 6 of 8 have been completed 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.841: [realtek] Enroll entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.841: Device reported finger status change: FP_FINGER_STATUS_NEEDED 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.842: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.842: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.842: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.842: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.842: [realtek] Enroll entering state 3 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.842: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.843: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.843: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.843: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.844: Device reported finger status change: FP_FINGER_STATUS_PRESENT 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.844: [realtek] Enroll entering state 4 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.844: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.844: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.844: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.845: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.845: Device reported finger status change: FP_FINGER_STATUS_NONE 134s (process:4014): libfprint-device-DEBUG: 03:38:01.845: Device reported enroll progress, reported 7 of 8 have been completed 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.845: [realtek] Enroll entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.845: Device reported finger status change: FP_FINGER_STATUS_NEEDED 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.845: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.846: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.846: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.846: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.846: [realtek] Enroll entering state 3 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.846: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.847: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.847: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.848: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.848: Device reported finger status change: FP_FINGER_STATUS_PRESENT 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.848: [realtek] Enroll entering state 4 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.848: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.848: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.849: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.849: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.850: Device reported finger status change: FP_FINGER_STATUS_NONE 134s (process:4014): libfprint-device-DEBUG: 03:38:01.850: Device reported enroll progress, reported 8 of 8 have been completed 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.850: [realtek] Enroll entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.850: Device reported finger status change: FP_FINGER_STATUS_NEEDED 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.850: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.850: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.850: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.850: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.851: [realtek] Enroll entering state 3 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.851: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.851: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.851: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.852: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.852: Device reported finger status change: FP_FINGER_STATUS_PRESENT 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.852: [realtek] Enroll entering state 4 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.852: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.853: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.853: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.853: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.854: Device reported finger status change: FP_FINGER_STATUS_NONE 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.854: [realtek] Enroll entering state 5 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.854: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.854: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.854: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.855: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.856: [realtek] Enroll entering state 6 134s (process:4014): libfprint-realtek-DEBUG: 03:38:01.856: user_id: FP1-00000000-0-00000000-nobody, finger: 0xff 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.856: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.856: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.856: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.857: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.857: [realtek] Enroll completed successfully 134s (process:4014): libfprint-realtek-DEBUG: 03:38:01.857: Enrollment complete! 134s (process:4014): libfprint-device-DEBUG: 03:38:01.857: Device reported enroll completion 134s (process:4014): libfprint-device-DEBUG: 03:38:01.857: Print for finger FP_FINGER_UNKNOWN enrolled 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.857: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-device-DEBUG: 03:38:01.857: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 134s (process:4014): libfprint-device-DEBUG: 03:38:01.857: Not updating temperature model, device can run continuously! 134s (process:4014): libfprint-realtek-DEBUG: 03:38:01.857: 81665394: ../libfprint/drivers/realtek/realtek.c:1345 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.857: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.858: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.858: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-realtek-DEBUG: 03:38:01.859: Query templates complete! 134s (process:4014): libfprint-device-DEBUG: 03:38:01.859: Device reported listing completion 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.859: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-device-DEBUG: 03:38:01.859: Completing action FPI_DEVICE_ACTION_LIST in idle! 134s (process:4014): libfprint-device-DEBUG: 03:38:01.859: Not updating temperature model, device can run continuously! 134s (process:4014): libfprint-device-DEBUG: 03:38:01.859: Not updating temperature model, device can run continuously! 134s (process:4014): libfprint-realtek-DEBUG: 03:38:01.859: 81667439: ../libfprint/drivers/realtek/realtek.c:1178 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.859: [realtek] Verify & Identify entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.859: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.860: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.860: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.861: [realtek] Verify & Identify entering state 1 134s (process:4014): libfprint-device-DEBUG: 03:38:01.861: Device reported finger status change: FP_FINGER_STATUS_NEEDED 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.861: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.861: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.861: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.861: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.862: [realtek] Verify & Identify entering state 2 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.862: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.862: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.863: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.863: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.864: Device reported finger status change: FP_FINGER_STATUS_PRESENT 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.864: [realtek] Verify & Identify entering state 3 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.864: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.864: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.864: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.865: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.865: Device reported finger status change: FP_FINGER_STATUS_NONE 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.865: [realtek] Verify & Identify entering state 4 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.865: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.866: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.866: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.866: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.867: Device reported verify result 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.867: [realtek] Verify & Identify entering state 5 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.867: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.867: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.867: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.867: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.868: [realtek] Verify & Identify completed successfully 134s (process:4014): libfprint-realtek-DEBUG: 03:38:01.868: Verify complete! 134s (process:4014): libfprint-device-DEBUG: 03:38:01.868: Device reported verify completion 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.868: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-device-DEBUG: 03:38:01.868: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 134s (process:4014): libfprint-device-DEBUG: 03:38:01.868: Not updating temperature model, device can run continuously! 134s (process:4014): libfprint-device-DEBUG: 03:38:01.869: Not updating temperature model, device can run continuously! 134s (process:4014): libfprint-realtek-DEBUG: 03:38:01.869: 81676738: ../libfprint/drivers/realtek/realtek.c:1178 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.869: [realtek] Verify & Identify entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.869: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.869: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.870: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.870: [realtek] Verify & Identify entering state 1 134s (process:4014): libfprint-device-DEBUG: 03:38:01.870: Device reported finger status change: FP_FINGER_STATUS_NEEDED 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.870: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.874: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.874: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.874: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.875: [realtek] Verify & Identify entering state 2 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.875: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.875: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.875: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.876: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.876: Device reported finger status change: FP_FINGER_STATUS_PRESENT 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.876: [realtek] Verify & Identify entering state 3 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.876: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.877: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.877: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.878: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.878: Device reported finger status change: FP_FINGER_STATUS_NONE 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.878: [realtek] Verify & Identify entering state 4 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.878: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.878: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.879: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.879: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-device-DEBUG: 03:38:01.880: Device reported identify result 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.880: [realtek] Verify & Identify completed successfully 134s (process:4014): libfprint-realtek-DEBUG: 03:38:01.880: Verify complete! 134s (process:4014): libfprint-device-DEBUG: 03:38:01.880: Device reported identify completion 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.880: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-device-DEBUG: 03:38:01.880: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 134s (process:4014): libfprint-device-DEBUG: 03:38:01.880: Not updating temperature model, device can run continuously! 134s (process:4014): libfprint-realtek-DEBUG: 03:38:01.880: 81688264: ../libfprint/drivers/realtek/realtek.c:1314 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.880: [realtek] Delete print entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.880: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.881: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.881: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.882: [realtek] Delete print entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.882: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.882: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.882: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.882: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.883: [realtek] Delete print completed successfully 134s (process:4014): libfprint-realtek-DEBUG: 03:38:01.883: Delete print complete! 134s (process:4014): libfprint-device-DEBUG: 03:38:01.883: Device reported deletion completion 134s (process:4014): libfprint-SSM-DEBUG: 03:38:01.883: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 134s (process:4014): libfprint-device-DEBUG: 03:38:01.883: Completing action FPI_DEVICE_ACTION_DELETE in idle! 134s (process:4014): libfprint-device-DEBUG: 03:38:01.883: Not updating temperature model, device can run continuously! 134s (process:4014): libfprint-realtek-DEBUG: 03:38:01.883: 81691118: ../libfprint/drivers/realtek/realtek.c:1302 134s (process:4014): libfprint-device-DEBUG: 03:38:01.883: Device reported close completion 134s (process:4014): libfprint-device-DEBUG: 03:38:01.883: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 134s (process:4014): libfprint-device-DEBUG: 03:38:01.883: Not updating temperature model, device can run continuously! 134s enrolling 134s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x6830d528a340 (FpiDeviceRealtek at 0x20d9c010)>, 1, None, None, None) 134s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x6830d528a340 (FpiDeviceRealtek at 0x20d9c010)>, 2, None, None, None) 134s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x6830d528a340 (FpiDeviceRealtek at 0x20d9c010)>, 3, None, None, None) 134s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x6830d528a340 (FpiDeviceRealtek at 0x20d9c010)>, 4, None, None, None) 134s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x6830d528a340 (FpiDeviceRealtek at 0x20d9c010)>, 5, None, None, None) 134s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x6830d528a340 (FpiDeviceRealtek at 0x20d9c010)>, 6, None, None, None) 134s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x6830d528a340 (FpiDeviceRealtek at 0x20d9c010)>, 7, None, None, None) 134s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x6830d528a340 (FpiDeviceRealtek at 0x20d9c010)>, 8, None, None, None) 134s enroll done 134s listing 134s listing done 134s verifying 134s verify done 134s async identifying 134s indentification_done: 134s deleting 134s delete done 134s ** (umockdev-run:4010): DEBUG: 03:38:01.896: umockdev.vala:154: Removing test bed /tmp/umockdev.07AG22 134s (umockdev-run:4010): GLib-DEBUG: 03:38:01.903: unsetenv() is not thread-safe and should not be used after threads are created 134s PASS: libfprint-2/driver-realtek.test 134s Running test: libfprint-2/driver-egismoc-0586.test 134s ** (umockdev-run:4022): DEBUG: 03:38:01.949: umockdev.vala:127: Created udev test bed /tmp/umockdev.TAYK22 134s ** (umockdev-run:4022): DEBUG: 03:38:01.949: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-7 134s ** (umockdev-run:4022): DEBUG: 03:38:01.950: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-7 (subsystem usb) 134s ** (umockdev-run:4022): DEBUG: 03:38:01.954: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.TAYK22/dev/bus/usb/001/021 134s ** (umockdev-run:4022): DEBUG: 03:38:01.954: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 134s ** (umockdev-run:4022): DEBUG: 03:38:01.955: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 134s ** (umockdev-run:4022): DEBUG: 03:38:01.958: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.TAYK22/dev/bus/usb/001/001 134s ** (umockdev-run:4022): DEBUG: 03:38:01.958: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 134s ** (umockdev-run:4022): DEBUG: 03:38:01.958: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 135s (process:4026): libfprint-context-DEBUG: 03:38:02.041: Initializing FpContext (libfprint version 1.94.8+tod1) 135s (process:4026): libfprint-tod-DEBUG: 03:38:02.041: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.043: 81851342: ../libfprint/drivers/egismoc/egismoc.c:1597 135s (process:4026): libfprint-context-DEBUG: 03:38:02.043: No driver found for USB device 1D6B:0002 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.044: egismoc_probe enter --> 135s (process:4026): libfprint-device-DEBUG: 03:38:02.045: Device reported probe completion 135s (process:4026): libfprint-device-DEBUG: 03:38:02.045: Completing action FPI_DEVICE_ACTION_PROBE in idle! 135s (process:4026): libfprint-device-DEBUG: 03:38:02.045: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.046: Opening device 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.046: [egismoc] DEV_INIT_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.047: [egismoc] DEV_INIT_STATES entering state 1 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.047: [egismoc] DEV_INIT_STATES entering state 2 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.048: [egismoc] DEV_INIT_STATES entering state 3 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.050: [egismoc] DEV_INIT_STATES entering state 4 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.051: [egismoc] DEV_INIT_STATES entering state 5 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.051: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.051: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.051: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.052: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.052: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.052: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.052: Firmware version callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.052: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.052: Device firmware version is 9050.6.2.56 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.052: [egismoc] DEV_INIT_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.052: Task SSM done 135s (process:4026): libfprint-device-DEBUG: 03:38:02.052: Device reported open completion 135s (process:4026): libfprint-device-DEBUG: 03:38:02.052: Completing action FPI_DEVICE_ACTION_OPEN in idle! 135s (process:4026): libfprint-device-DEBUG: 03:38:02.053: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.053: List 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.053: [egismoc] LIST_STATES entering state 0 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.053: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.053: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.053: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.054: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.054: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.054: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.054: List callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.054: Device fingerprint 1: FP1-20240417-7-67C37FA4-root 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.054: Number of currently enrolled fingerprints on the device is 1 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.054: [egismoc] LIST_STATES entering state 1 135s (process:4026): libfprint-device-DEBUG: 03:38:02.054: Device reported listing completion 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.055: [egismoc] LIST_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.055: Task SSM done 135s (process:4026): libfprint-device-DEBUG: 03:38:02.055: Completing action FPI_DEVICE_ACTION_LIST in idle! 135s (process:4026): libfprint-device-DEBUG: 03:38:02.055: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.055: Clear storage 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.055: [egismoc] DELETE_STATES entering state 0 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.055: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.055: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.055: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.055: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.056: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.056: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.056: List callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.056: Device fingerprint 1: FP1-20240417-7-67C37FA4-root 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.056: Number of currently enrolled fingerprints on the device is 1 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.056: [egismoc] DELETE_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.056: Get delete command 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.056: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.056: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.056: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.057: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.057: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.057: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.057: Delete callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.058: Response prefix valid: yes 135s (process:4026): libfprint-device-DEBUG: 03:38:02.058: Device reported deletion completion 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.058: [egismoc] DELETE_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.058: Task SSM done 135s (process:4026): libfprint-device-DEBUG: 03:38:02.058: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 135s (process:4026): libfprint-device-DEBUG: 03:38:02.058: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.058: List 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.058: [egismoc] LIST_STATES entering state 0 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.058: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.058: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.058: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.059: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.059: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.059: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.059: List callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.059: Number of currently enrolled fingerprints on the device is 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.059: [egismoc] LIST_STATES entering state 1 135s (process:4026): libfprint-device-DEBUG: 03:38:02.059: Device reported listing completion 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.059: [egismoc] LIST_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.059: Task SSM done 135s (process:4026): libfprint-device-DEBUG: 03:38:02.059: Completing action FPI_DEVICE_ACTION_LIST in idle! 135s (process:4026): libfprint-device-DEBUG: 03:38:02.059: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s (process:4026): libfprint-device-DEBUG: 03:38:02.060: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.060: Enroll 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.060: [egismoc] ENROLL_STATES entering state 0 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.060: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.060: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.060: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.060: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.061: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.061: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.061: List callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.061: Number of currently enrolled fingerprints on the device is 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.061: [egismoc] ENROLL_STATES entering state 1 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.061: [egismoc] ENROLL_STATES entering state 2 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.061: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.061: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.061: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.062: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.062: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.062: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.062: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.062: [egismoc] ENROLL_STATES entering state 3 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.062: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.062: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.063: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.063: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.064: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.064: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.064: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.064: [egismoc] ENROLL_STATES entering state 4 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.064: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.064: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.064: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.064: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.064: [egismoc] ENROLL_STATES entering state 5 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.064: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.064: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.064: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.065: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.065: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.065: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.065: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.065: [egismoc] ENROLL_STATES entering state 6 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.065: Get check command 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.065: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.065: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.065: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.066: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.066: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.066: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.066: Enroll check callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.066: Response suffix valid: yes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.066: [egismoc] ENROLL_STATES entering state 7 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.066: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.066: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.066: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.067: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.068: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.068: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.068: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.068: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.068: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.068: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.068: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.068: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.069: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.069: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.069: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.069: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.069: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.069: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.069: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.069: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.070: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.070: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.070: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.070: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.070: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.070: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.071: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.071: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.071: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.071: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.071: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.071: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.071: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.072: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.072: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.072: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.072: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.072: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.072: Partial capture successful. Please touch the sensor again (1/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.072: Device reported enroll progress, reported 1 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.072: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.072: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.072: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.072: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.073: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.073: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.073: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.073: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.073: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.073: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.073: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.073: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.074: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.075: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.075: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.075: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.075: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.075: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.075: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.075: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.075: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.075: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.075: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.075: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.075: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.076: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.077: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.077: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.077: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.077: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.077: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.077: Partial capture successful. Please touch the sensor again (2/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.077: Device reported enroll progress, reported 2 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.077: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.077: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.077: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.077: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.077: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.078: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.078: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.078: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.078: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.078: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.078: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.078: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.078: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.079: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.079: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.079: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.079: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.079: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.079: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.080: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.080: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.080: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.080: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.080: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.080: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.080: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.081: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.081: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.081: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.081: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.081: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.081: Partial capture successful. Please touch the sensor again (3/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.081: Device reported enroll progress, reported 3 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.081: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.081: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.081: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.081: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.081: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.082: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.082: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.082: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.082: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.082: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.082: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.082: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.082: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.083: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.083: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.083: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.083: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.083: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.083: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.084: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.084: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.084: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.084: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.084: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.084: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.084: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.085: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.085: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.085: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.085: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.085: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.085: Partial capture successful. Please touch the sensor again (4/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.085: Device reported enroll progress, reported 4 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.085: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.085: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.085: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.085: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.085: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.087: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.087: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.087: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.087: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.087: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.087: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.087: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.087: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.088: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.088: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.088: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.088: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.088: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.088: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.089: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.089: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.089: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.089: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.089: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.089: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.089: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.090: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.090: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.090: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.090: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.090: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.090: Partial capture successful. Please touch the sensor again (5/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.090: Device reported enroll progress, reported 5 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.090: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.090: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.090: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.090: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.090: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.091: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.091: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.091: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.091: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.091: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.091: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.091: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.092: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.092: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.092: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.092: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.092: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.092: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.092: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.093: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.093: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.093: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.093: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.093: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.093: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.093: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.094: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.094: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.094: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.094: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.094: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.094: Partial capture successful. Please touch the sensor again (6/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.094: Device reported enroll progress, reported 6 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.094: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.094: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.094: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.094: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.095: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.095: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.095: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.095: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.095: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.095: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.095: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.095: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.096: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.096: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.096: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.096: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.096: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.096: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.096: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.097: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.097: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.097: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.097: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.097: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.097: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.097: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.098: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.098: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.098: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.098: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.098: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.098: Partial capture successful. Please touch the sensor again (7/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.098: Device reported enroll progress, reported 7 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.098: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.098: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.098: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.098: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.098: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.099: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.099: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.099: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.099: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.099: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.099: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.099: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.100: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.100: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.100: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.100: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.100: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.100: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.100: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.101: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.101: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.101: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.101: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.101: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.101: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.101: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.102: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.102: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.102: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.102: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.102: Response suffix valid: NO 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.102: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.102: Response suffix valid: yes 135s (process:4026): libfprint-device-DEBUG: 03:38:02.102: Device reported enroll progress, reported 7 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.102: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.102: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.102: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.102: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.102: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.103: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.103: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.103: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.103: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.103: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.103: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.103: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.103: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.104: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.104: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.104: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.104: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.104: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.104: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.104: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.104: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.104: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.104: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.104: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.104: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.105: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.105: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.106: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.106: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.106: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.106: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.106: Partial capture successful. Please touch the sensor again (8/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.106: Device reported enroll progress, reported 8 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.106: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.106: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.106: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.106: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.106: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.107: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.107: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.107: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.107: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.107: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.107: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.107: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.107: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.108: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.108: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.108: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.108: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.108: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.108: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.108: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.108: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.108: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.108: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.108: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.108: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.109: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.109: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.109: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.109: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.109: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.109: Response suffix valid: NO 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.109: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.109: Response suffix valid: yes 135s (process:4026): libfprint-device-DEBUG: 03:38:02.109: Device reported enroll progress, reported 8 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.109: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.109: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.109: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.109: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.110: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.111: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.111: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.111: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.111: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.111: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.111: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.111: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.111: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.114: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.114: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.114: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.114: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.114: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.114: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.115: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.115: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.115: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.115: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.115: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.115: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.115: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.116: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.116: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.116: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.116: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.116: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.116: Partial capture successful. Please touch the sensor again (9/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.116: Device reported enroll progress, reported 9 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.116: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.116: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.116: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.116: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.116: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.117: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.117: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.117: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.117: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.117: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.117: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.117: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.118: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.118: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.118: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.118: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.118: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.118: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.118: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.119: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.119: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.119: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.119: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.119: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.119: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.119: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.120: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.120: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.120: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.120: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.120: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.120: Partial capture successful. Please touch the sensor again (10/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.120: Device reported enroll progress, reported 10 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.120: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.120: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.120: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.120: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.120: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.121: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.121: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.121: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.121: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.121: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.121: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.121: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.121: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.122: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.122: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.122: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.122: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.122: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.122: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.123: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.123: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.123: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.123: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.123: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.123: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.123: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.124: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.124: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.124: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.124: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.124: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.124: Partial capture successful. Please touch the sensor again (11/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.124: Device reported enroll progress, reported 11 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.124: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.124: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.124: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.124: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.125: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.125: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.126: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.126: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.126: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.126: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.126: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.126: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.126: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.127: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.127: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.127: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.127: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.127: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.127: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.127: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.127: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.127: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.127: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.127: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.127: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.128: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.128: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.128: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.128: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.128: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.128: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.128: Partial capture successful. Please touch the sensor again (12/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.128: Device reported enroll progress, reported 12 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.129: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.129: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.129: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.129: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.129: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.134: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.134: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.134: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.134: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.134: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.134: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.134: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.135: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.135: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.136: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.136: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.136: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.136: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.136: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.136: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.136: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.136: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.136: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.136: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.136: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.137: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.137: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.137: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.137: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.137: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.137: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.137: Partial capture successful. Please touch the sensor again (13/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.137: Device reported enroll progress, reported 13 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.137: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.137: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.137: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.137: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.138: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.139: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.139: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.139: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.139: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.139: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.139: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.139: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.140: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.140: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.140: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.140: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.140: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.140: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.140: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.141: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.141: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.141: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.141: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.141: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.141: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.141: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.142: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.142: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.142: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.142: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.142: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.142: Partial capture successful. Please touch the sensor again (14/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.142: Device reported enroll progress, reported 14 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.142: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.142: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.142: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.142: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.143: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.143: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.143: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.143: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.143: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.143: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.143: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.143: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.144: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.144: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.144: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.144: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.144: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.144: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.144: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.145: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.145: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.145: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.145: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.145: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.145: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.145: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.146: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.146: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.146: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.146: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.146: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.146: Partial capture successful. Please touch the sensor again (15/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.146: Device reported enroll progress, reported 15 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.146: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.146: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.146: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.146: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.146: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.147: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.147: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.147: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.147: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.147: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.147: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.147: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.148: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.148: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.148: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.148: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.148: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.148: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.148: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.149: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.149: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.149: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.149: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.149: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.149: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.149: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.150: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.150: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.150: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.150: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.150: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.150: Partial capture successful. Please touch the sensor again (16/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.150: Device reported enroll progress, reported 16 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.150: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.150: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.150: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.150: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.151: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.151: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.151: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.151: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.151: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.151: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.151: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.151: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.154: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.155: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.155: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.155: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.155: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.155: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.155: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.155: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.155: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.155: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.155: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.155: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.155: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.156: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.157: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.157: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.157: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.157: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.157: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.157: Partial capture successful. Please touch the sensor again (17/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.157: Device reported enroll progress, reported 17 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.157: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.157: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.157: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.157: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.157: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.158: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.158: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.158: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.158: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.158: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.158: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.158: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.159: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.159: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.159: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.159: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.159: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.159: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.159: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.160: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.160: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.160: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.160: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.160: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.160: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.160: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.161: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.161: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.161: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.161: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.161: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.161: Partial capture successful. Please touch the sensor again (18/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.161: Device reported enroll progress, reported 18 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.161: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.161: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.161: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.161: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.161: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-device-DEBUG: 03:38:02.162: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.162: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.162: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.162: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.162: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.162: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.162: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.162: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.162: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.163: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.163: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.163: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.163: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.163: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.163: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.164: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.164: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.164: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.164: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.164: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.164: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.164: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.165: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.165: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.165: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.165: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.165: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.165: Partial capture successful. Please touch the sensor again (19/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.165: Device reported enroll progress, reported 19 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.165: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.165: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.165: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.165: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.165: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.166: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.166: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.166: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.166: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.166: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.166: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.166: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.167: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.167: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.167: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.167: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.167: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.167: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.167: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.168: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.168: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.168: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.168: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.168: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.168: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.168: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.169: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.169: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.169: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.169: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.169: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.169: Partial capture successful. Please touch the sensor again (20/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.169: Device reported enroll progress, reported 20 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.169: [egismoc] ENROLL_STATES entering state 12 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.169: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.169: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.169: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.169: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.170: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.170: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.170: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.170: [egismoc] ENROLL_STATES entering state 13 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.170: New fingerprint ID: FP1-00000000-2-00000000-nobody 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.170: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.170: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.170: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.171: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.171: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.171: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.171: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.171: [egismoc] ENROLL_STATES entering state 14 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.171: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.171: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.171: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.172: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.172: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.172: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.172: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.173: [egismoc] ENROLL_STATES entering state 15 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.173: Enrollment was successful! 135s (process:4026): libfprint-device-DEBUG: 03:38:02.173: Device reported enroll completion 135s (process:4026): libfprint-device-DEBUG: 03:38:02.173: Device reported finger status change: FP_FINGER_STATUS_NONE 135s (process:4026): libfprint-device-DEBUG: 03:38:02.173: Print for finger FP_FINGER_LEFT_INDEX enrolled 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.173: [egismoc] ENROLL_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.173: Task SSM done 135s (process:4026): libfprint-device-DEBUG: 03:38:02.173: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 135s (process:4026): libfprint-device-DEBUG: 03:38:02.173: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.173: List 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.173: [egismoc] LIST_STATES entering state 0 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.173: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.173: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.173: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.173: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.174: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.174: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.174: List callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.174: Device fingerprint 1: FP1-00000000-2-00000000-nobody 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.174: Number of currently enrolled fingerprints on the device is 1 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.174: [egismoc] LIST_STATES entering state 1 135s (process:4026): libfprint-device-DEBUG: 03:38:02.174: Device reported listing completion 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.174: [egismoc] LIST_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.174: Task SSM done 135s (process:4026): libfprint-device-DEBUG: 03:38:02.174: Completing action FPI_DEVICE_ACTION_LIST in idle! 135s (process:4026): libfprint-device-DEBUG: 03:38:02.174: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:4026): libfprint-device-DEBUG: 03:38:02.174: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.174: Identify or Verify 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.174: [egismoc] IDENTIFY_STATES entering state 0 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.174: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.174: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.174: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.175: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.175: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.175: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.175: List callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.175: Device fingerprint 1: FP1-00000000-2-00000000-nobody 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.175: Number of currently enrolled fingerprints on the device is 1 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.175: [egismoc] IDENTIFY_STATES entering state 1 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.176: [egismoc] IDENTIFY_STATES entering state 2 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.176: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.176: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.176: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.176: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.177: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.177: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.177: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.177: [egismoc] IDENTIFY_STATES entering state 3 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.177: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.177: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.177: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.177: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.178: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.178: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.178: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.178: [egismoc] IDENTIFY_STATES entering state 4 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.178: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.178: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.178: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.178: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.178: [egismoc] IDENTIFY_STATES entering state 5 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.178: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.178: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.178: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.179: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.179: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.179: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.179: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.179: [egismoc] IDENTIFY_STATES entering state 6 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.179: Get check command 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.179: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.179: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.179: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.180: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.180: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.180: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.180: Identify check callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.180: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.180: Identify successful for: FP1-00000000-2-00000000-nobody 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.180: Verifying against: FP1-00000000-2-00000000-nobody 135s (process:4026): libfprint-device-DEBUG: 03:38:02.181: Device reported verify result 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.181: [egismoc] IDENTIFY_STATES entering state 7 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.181: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.181: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.181: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.181: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.182: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.182: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.182: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.182: [egismoc] IDENTIFY_STATES entering state 8 135s (process:4026): libfprint-device-DEBUG: 03:38:02.182: Device reported verify completion 135s (process:4026): libfprint-device-DEBUG: 03:38:02.182: Device reported finger status change: FP_FINGER_STATUS_NONE 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.182: [egismoc] IDENTIFY_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.182: Task SSM done 135s (process:4026): libfprint-device-DEBUG: 03:38:02.182: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 135s (process:4026): libfprint-device-DEBUG: 03:38:02.182: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:4026): libfprint-device-DEBUG: 03:38:02.182: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.182: Identify or Verify 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.182: [egismoc] IDENTIFY_STATES entering state 0 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.182: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.182: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.182: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.183: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.183: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.183: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.183: List callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.183: Device fingerprint 1: FP1-00000000-2-00000000-nobody 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.184: Number of currently enrolled fingerprints on the device is 1 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.184: [egismoc] IDENTIFY_STATES entering state 1 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.184: [egismoc] IDENTIFY_STATES entering state 2 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.184: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.184: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.184: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.184: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.185: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.185: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.185: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.185: [egismoc] IDENTIFY_STATES entering state 3 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.185: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.185: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.185: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.186: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.186: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.186: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.186: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.186: [egismoc] IDENTIFY_STATES entering state 4 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.186: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.186: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.190: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.190: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.190: [egismoc] IDENTIFY_STATES entering state 5 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.190: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.190: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.190: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.192: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.192: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.192: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.192: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.192: [egismoc] IDENTIFY_STATES entering state 6 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.192: Get check command 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.192: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.192: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.192: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.193: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.193: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.193: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.193: Identify check callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.193: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.193: Identify successful for: FP1-00000000-2-00000000-nobody 135s (process:4026): libfprint-device-DEBUG: 03:38:02.193: Device reported identify result 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.193: [egismoc] IDENTIFY_STATES entering state 7 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.194: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.194: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.194: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.194: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.195: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.195: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.195: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.195: [egismoc] IDENTIFY_STATES entering state 8 135s (process:4026): libfprint-device-DEBUG: 03:38:02.195: Device reported identify completion 135s (process:4026): libfprint-device-DEBUG: 03:38:02.195: Device reported finger status change: FP_FINGER_STATUS_NONE 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.195: [egismoc] IDENTIFY_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.195: Task SSM done 135s (process:4026): libfprint-device-DEBUG: 03:38:02.195: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 135s (process:4026): libfprint-device-DEBUG: 03:38:02.195: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:4026): libfprint-device-DEBUG: 03:38:02.195: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.195: Enroll 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.195: [egismoc] ENROLL_STATES entering state 0 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.195: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.195: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.195: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.196: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.196: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.196: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.196: List callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.197: Device fingerprint 1: FP1-00000000-2-00000000-nobody 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.197: Number of currently enrolled fingerprints on the device is 1 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.197: [egismoc] ENROLL_STATES entering state 1 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.197: [egismoc] ENROLL_STATES entering state 2 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.197: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.197: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.197: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.197: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.198: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.198: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.198: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.198: [egismoc] ENROLL_STATES entering state 3 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.198: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.198: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.198: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.202: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.203: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.203: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.203: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.203: [egismoc] ENROLL_STATES entering state 4 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.203: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.203: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.204: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.204: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.204: [egismoc] ENROLL_STATES entering state 5 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.204: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.204: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.204: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.204: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.205: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.205: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.205: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.205: [egismoc] ENROLL_STATES entering state 6 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.205: Get check command 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.205: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.205: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.205: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.205: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.206: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.206: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.206: Enroll check callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.206: Response suffix valid: NO 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.206: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.206: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.206: Task SSM done 135s (process:4026): libfprint-device-DEBUG: 03:38:02.206: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL 135s (process:4026): libfprint-device-DEBUG: 03:38:02.206: Device reported enroll completion 135s (process:4026): libfprint-device-DEBUG: 03:38:02.206: Device reported finger status change: FP_FINGER_STATUS_NONE 135s (process:4026): libfprint-device-DEBUG: 03:38:02.206: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 135s (process:4026): libfprint-device-DEBUG: 03:38:02.206: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.206: List 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.206: [egismoc] LIST_STATES entering state 0 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.206: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.206: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.206: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.207: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.208: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.208: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.208: List callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.208: Device fingerprint 1: FP1-00000000-2-00000000-nobody 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.208: Number of currently enrolled fingerprints on the device is 1 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.208: [egismoc] LIST_STATES entering state 1 135s (process:4026): libfprint-device-DEBUG: 03:38:02.208: Device reported listing completion 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.208: [egismoc] LIST_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.208: Task SSM done 135s (process:4026): libfprint-device-DEBUG: 03:38:02.208: Completing action FPI_DEVICE_ACTION_LIST in idle! 135s (process:4026): libfprint-device-DEBUG: 03:38:02.208: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:4026): libfprint-device-DEBUG: 03:38:02.208: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.208: Enroll 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.208: [egismoc] ENROLL_STATES entering state 0 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.208: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.208: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.208: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.208: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.209: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.209: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.209: List callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.209: Device fingerprint 1: FP1-00000000-2-00000000-nobody 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.209: Number of currently enrolled fingerprints on the device is 1 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.209: [egismoc] ENROLL_STATES entering state 1 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.209: [egismoc] ENROLL_STATES entering state 2 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.209: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.209: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.209: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.210: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.210: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.210: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.210: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.210: [egismoc] ENROLL_STATES entering state 3 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.210: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.210: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.210: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.211: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.212: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.212: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.212: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.212: [egismoc] ENROLL_STATES entering state 4 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.212: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.212: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.212: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.212: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.212: [egismoc] ENROLL_STATES entering state 5 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.212: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.212: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.212: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.213: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.213: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.213: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.213: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.213: [egismoc] ENROLL_STATES entering state 6 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.213: Get check command 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.213: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.213: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.213: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.214: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.214: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.214: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.214: Enroll check callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.214: Response suffix valid: yes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.214: [egismoc] ENROLL_STATES entering state 7 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.214: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.214: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.214: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.215: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.215: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.215: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.215: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.215: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.215: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.215: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.215: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.216: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.216: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.216: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.217: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.217: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.217: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.217: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.217: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.217: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.217: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.217: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.217: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.218: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.218: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.218: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.218: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.218: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.218: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.218: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.218: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.218: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.218: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.219: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.219: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.219: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.219: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.219: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.219: Partial capture successful. Please touch the sensor again (1/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.219: Device reported enroll progress, reported 1 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.219: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.219: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.219: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.219: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.220: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.220: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.220: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.220: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.220: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.220: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.220: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.220: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.221: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.221: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.221: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.221: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.221: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.221: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.221: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.222: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.222: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.222: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.222: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.222: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.222: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.222: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.223: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.223: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.223: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.223: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.223: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.223: Partial capture successful. Please touch the sensor again (2/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.223: Device reported enroll progress, reported 2 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.223: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.223: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.223: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.223: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.224: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.224: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.224: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.224: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.224: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.224: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.224: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.224: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.225: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.225: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.225: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.225: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.225: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.225: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.225: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.226: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.226: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.226: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.226: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.226: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.226: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.226: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.227: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.227: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.227: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.227: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.227: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.227: Partial capture successful. Please touch the sensor again (3/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.227: Device reported enroll progress, reported 3 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.227: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.227: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.227: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.227: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.227: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.228: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.228: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.228: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.228: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.228: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.228: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.228: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.228: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.229: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.229: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.229: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.229: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.229: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.229: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.230: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.230: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.230: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.230: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.230: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.230: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.230: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.231: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.231: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.231: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.231: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.231: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.231: Partial capture successful. Please touch the sensor again (4/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.231: Device reported enroll progress, reported 4 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.231: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.231: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.231: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.231: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.231: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.232: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.232: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.232: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.232: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.232: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.232: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.232: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.232: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.233: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.233: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.233: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.233: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.233: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.233: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.233: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.234: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.234: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.234: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.234: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.234: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.234: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.235: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.235: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.235: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.235: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.235: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.235: Partial capture successful. Please touch the sensor again (5/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.235: Device reported enroll progress, reported 5 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.235: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.235: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.235: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.235: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.235: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.236: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.236: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.236: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.236: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.236: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.236: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.236: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.236: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.237: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.237: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.237: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.237: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.237: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.237: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.238: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.238: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.238: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.238: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.238: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.238: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.238: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.239: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.239: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.239: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.239: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.239: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.239: Partial capture successful. Please touch the sensor again (6/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.239: Device reported enroll progress, reported 6 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.239: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.239: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.239: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.239: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.239: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.240: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.240: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.240: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.240: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.240: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.240: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.240: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.240: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.241: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.241: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.241: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.241: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.241: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.241: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.241: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.242: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.242: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.242: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.242: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.242: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.242: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.246: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.246: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.246: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.246: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.246: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.246: Partial capture successful. Please touch the sensor again (7/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.246: 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 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 1, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 2, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 3, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 4, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 5, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 6, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 7, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 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 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 8, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 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 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 9, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 10, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 11, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 12, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 13, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 14, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 15, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 16, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 17, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 18, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 19, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 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 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 1, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 2, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 3, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 4, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 5, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 6, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 7, , None, None)(process:4026): libfprint-SSM-DEBUG: 03:38:02.246: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.246: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.246: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.246: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.247: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.248: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.248: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.248: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.248: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.248: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.248: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.248: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.248: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.249: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.249: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.249: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.249: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.249: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.249: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.249: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.249: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.249: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.249: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.249: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.249: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.250: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.250: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.251: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.251: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.251: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.251: Response suffix valid: NO 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.251: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.251: Response suffix valid: yes 135s (process:4026): libfprint-device-DEBUG: 03:38:02.251: Device reported enroll progress, reported 7 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.251: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.251: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.251: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.251: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.251: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.252: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.252: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.252: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.252: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.252: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.252: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.252: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.252: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.253: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.253: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.253: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.253: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.253: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.253: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.253: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.253: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.253: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.253: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.253: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.253: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.254: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.255: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.255: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.255: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.255: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.255: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.255: Partial capture successful. Please touch the sensor again (8/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.255: Device reported enroll progress, reported 8 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.255: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.255: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.255: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.255: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.256: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.256: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.257: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.257: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.257: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.257: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.257: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.257: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.257: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.258: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.258: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.258: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.258: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.258: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.258: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.258: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.258: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.258: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.258: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.258: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.258: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.259: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.259: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.259: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.259: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.259: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.259: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.259: Partial capture successful. Please touch the sensor again (9/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.259: Device reported enroll progress, reported 9 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.259: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.259: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.259: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.259: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.260: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.261: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.261: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.261: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.261: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.261: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.261: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.261: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.261: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.262: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.262: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.262: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.262: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.262: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.262: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.262: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.263: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.263: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.263: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.263: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.263: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.263: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.264: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.264: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.264: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.264: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.264: Response suffix valid: NO 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.264: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.264: Response suffix valid: yes 135s (process:4026): libfprint-device-DEBUG: 03:38:02.264: Device reported enroll progress, reported 9 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.264: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.264: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.264: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.264: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.265: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.265: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.265: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.265: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.265: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.265: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.265: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.265: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.266: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.266: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.266: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.266: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.266: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.266: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.266: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.267: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.267: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.267: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.267: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.267: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.267: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.268: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.268: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.268: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.268: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.268: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.268: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.268: Partial capture successful. Please touch the sensor again (10/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.268: Device reported enroll progress, reported 10 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.268: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.268: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.268: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.268: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.270: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.271: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.271: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.271: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.271: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.271: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.271: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.271: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.271: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.272: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.272: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.272: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.272: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.272: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.272: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.273: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.273: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.273: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.273: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.273: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.273: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.273: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.274: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.274: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.274: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.274: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.274: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.274: Partial capture successful. Please touch the sensor again (11/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.274: Device reported enroll progress, reported 11 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.274: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.274: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.274: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.274: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.274: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.275: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.275: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.275: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.275: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.275: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.275: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.275: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.275: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.276: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.276: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.276: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.276: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.276: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.276: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.277: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.277: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.277: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.277: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.277: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.277: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.277: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.278: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.278: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.278: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.278: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.278: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.278: Partial capture successful. Please touch the sensor again (12/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.278: Device reported enroll progress, reported 12 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.278: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.278: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.278: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.278: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.278: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.279: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.279: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.279: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.279: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.279: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.279: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.279: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.280: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.280: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.280: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.280: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.280: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.280: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.280: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.282: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.282: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.282: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.282: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.282: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.282: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.283: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.283: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.283: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.283: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.283: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.283: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.283: Partial capture successful. Please touch the sensor again (13/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.283: Device reported enroll progress, reported 13 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.284: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.284: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.284: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.284: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.284: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.285: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.285: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.285: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.285: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.285: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.285: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.285: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.285: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.286: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.286: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.286: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.286: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.286: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.286: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.287: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.287: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.287: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.287: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.287: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.287: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.287: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.288: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.288: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.288: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.288: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.288: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.288: Partial capture successful. Please touch the sensor again (14/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.288: Device reported enroll progress, reported 14 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.288: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.288: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.288: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.288: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.288: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.289: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.289: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.289: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.289: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.289: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.289: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.289: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.290: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.290: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.290: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.290: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.290: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.290: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.290: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.291: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.291: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.291: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.291: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.291: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.291: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.291: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.292: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.292: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.292: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.292: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.292: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.292: Partial capture successful. Please touch the sensor again (15/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.292: Device reported enroll progress, reported 15 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.292: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.292: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.292: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.292: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.292: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.293: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.293: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.293: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.293: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.293: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.293: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.293: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.294: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.294: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.294: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.294: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.294: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.294: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.294: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.295: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.295: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.295: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.295: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.295: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.295: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.296: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.297: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.297: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.297: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.297: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.297: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.297: Partial capture successful. Please touch the sensor again (16/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.297: Device reported enroll progress, reported 16 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.297: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.297: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.297: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.297: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.297: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.298: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.298: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.298: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.298: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.298: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.298: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.298: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.299: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.300: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.300: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.300: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.300: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.300: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.300: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.300: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.300: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.300: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.300: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.300: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.300: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.301: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.301: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.301: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.301: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.301: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.301: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.302: Partial capture successful. Please touch the sensor again (17/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.302: Device reported enroll progress, reported 17 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.302: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.302: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.302: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.302: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.302: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.303: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.303: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.303: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.303: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.303: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.303: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.303: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.303: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.304: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.304: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.304: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.304: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.304: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.304: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.304: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.305: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.305: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.305: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.305: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.305: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.305: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.306: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.306: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.306: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.306: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.306: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.306: Partial capture successful. Please touch the sensor again (18/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.306: Device reported enroll progress, reported 18 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.306: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.306: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.306: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.306: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.307: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.307: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.307: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.307: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.307: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.307: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.307: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.307: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.308: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.309: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.309: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.309: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.309: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.309: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.309: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.309: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.309: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.309: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.309: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.309: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.309: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.310: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.310: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.310: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.310: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.310: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.310: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.310: Partial capture successful. Please touch the sensor again (19/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.310: Device reported enroll progress, reported 19 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.310: [egismoc] ENROLL_STATES entering state 8 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.310: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.310: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.310: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.311: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.311: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.311: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.311: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.312: [egismoc] ENROLL_STATES entering state 9 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.312: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.312: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.312: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.312: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.313: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.313: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.313: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.313: [egismoc] ENROLL_STATES entering state 10 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.313: Wait for finger on sensor 135s (process:4026): libfprint-device-DEBUG: 03:38:02.313: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.313: Finger on sensor callback 135s (process:4026): libfprint-device-DEBUG: 03:38:02.313: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.313: [egismoc] ENROLL_STATES entering state 11 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.313: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.313: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.313: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.314: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.314: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.314: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.314: Read capture callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.314: Response prefix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.314: Response suffix valid: yes 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.314: Partial capture successful. Please touch the sensor again (20/20) 135s (process:4026): libfprint-device-DEBUG: 03:38:02.314: Device reported enroll progress, reported 20 of 20 have been completed 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.314: [egismoc] ENROLL_STATES entering state 12 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.314: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.314: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.314: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.315: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.316: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.316: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.316: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.316: [egismoc] ENROLL_STATES entering state 13 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.316: New fingerprint ID: FP1-00000000-7-00000000-nobody 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.316: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.316: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.316: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.316: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.317: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.317: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.317: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.317: [egismoc] ENROLL_STATES entering state 14 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.317: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.317: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.317: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.317: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.318: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.318: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.318: Task SSM next state callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.318: [egismoc] ENROLL_STATES entering state 15 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.318: Enrollment was successful! 135s (process:4026): libfprint-device-DEBUG: 03:38:02.318: Device reported enroll completion 135s (process:4026): libfprint-device-DEBUG: 03:38:02.318: Device reported finger status change: FP_FINGER_STATUS_NONE 135s (process:4026): libfprint-device-DEBUG: 03:38:02.318: Print for finger FP_FINGER_RIGHT_INDEX enrolled 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.318: [egismoc] ENROLL_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.318: Task SSM done 135s (process:4026): libfprint-device-DEBUG: 03:38:02.318: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 135s (process:4026): libfprint-device-DEBUG: 03:38:02.318: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.318: List 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.318: [egismoc] LIST_STATES entering state 0 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.318: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.318: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.318: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.319: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.319: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.319: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.319: List callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.319: Device fingerprint 1: FP1-00000000-2-00000000-nobody 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.319: Device fingerprint 2: FP1-00000000-7-00000000-nobody 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.319: Number of currently enrolled fingerprints on the device is 2 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.319: [egismoc] LIST_STATES entering state 1 135s (process:4026): libfprint-device-DEBUG: 03:38:02.319: Device reported listing completion 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.319: [egismoc] LIST_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.319: Task SSM done 135s (process:4026): libfprint-device-DEBUG: 03:38:02.319: Completing action FPI_DEVICE_ACTION_LIST in idle! 135s (process:4026): libfprint-device-DEBUG: 03:38:02.319: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.320: Delete 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.320: [egismoc] DELETE_STATES entering state 0 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.320: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.320: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.320: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.320: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.321: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.321: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.321: List callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.321: Device fingerprint 1: FP1-00000000-2-00000000-nobody 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.321: Device fingerprint 2: FP1-00000000-7-00000000-nobody 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.321: Number of currently enrolled fingerprints on the device is 2 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.321: [egismoc] DELETE_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.321: Get delete command 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.321: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody) 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.321: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.321: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.321: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.322: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.322: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.322: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.322: Delete callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.322: Response prefix valid: yes 135s (process:4026): libfprint-device-DEBUG: 03:38:02.322: Device reported deletion completion 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.322: [egismoc] DELETE_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.322: Task SSM done 135s (process:4026): libfprint-device-DEBUG: 03:38:02.322: Completing action FPI_DEVICE_ACTION_DELETE in idle! 135s (process:4026): libfprint-device-DEBUG: 03:38:02.322: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.322: List 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.322: [egismoc] LIST_STATES entering state 0 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.322: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.322: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.322: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.323: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.323: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.323: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.323: List callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.323: Device fingerprint 1: FP1-00000000-7-00000000-nobody 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.324: Number of currently enrolled fingerprints on the device is 1 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.324: [egismoc] LIST_STATES entering state 1 135s (process:4026): libfprint-device-DEBUG: 03:38:02.324: Device reported listing completion 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.324: [egismoc] LIST_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.324: Task SSM done 135s (process:4026): libfprint-device-DEBUG: 03:38:02.324: Completing action FPI_DEVICE_ACTION_LIST in idle! 135s (process:4026): libfprint-device-DEBUG: 03:38:02.324: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.324: Clear storage 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.324: [egismoc] DELETE_STATES entering state 0 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.324: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.324: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.324: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.324: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.325: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.325: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.325: List callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.325: Device fingerprint 1: FP1-00000000-7-00000000-nobody 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.325: Number of currently enrolled fingerprints on the device is 1 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.325: [egismoc] DELETE_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.325: Get delete command 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.325: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.325: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.325: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.326: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.326: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.326: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.326: Delete callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.326: Response prefix valid: yes 135s (process:4026): libfprint-device-DEBUG: 03:38:02.326: Device reported deletion completion 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.326: [egismoc] DELETE_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.326: Task SSM done 135s (process:4026): libfprint-device-DEBUG: 03:38:02.326: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 135s (process:4026): libfprint-device-DEBUG: 03:38:02.326: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.326: List 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.326: [egismoc] LIST_STATES entering state 0 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.326: Execute command and get response 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.326: Get check bytes 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.326: [egismoc] CMD_STATES entering state 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.327: [egismoc] CMD_STATES entering state 1 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.328: Command receive callback 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.328: [egismoc] CMD_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.328: List callback 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.328: Number of currently enrolled fingerprints on the device is 0 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.328: [egismoc] LIST_STATES entering state 1 135s (process:4026): libfprint-device-DEBUG: 03:38:02.328: Device reported listing completion 135s (process:4026): libfprint-SSM-DEBUG: 03:38:02.328: [egismoc] LIST_STATES completed successfully 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.328: Task SSM done 135s (process:4026): libfprint-device-DEBUG: 03:38:02.328: Completing action FPI_DEVICE_ACTION_LIST in idle! 135s (process:4026): libfprint-device-DEBUG: 03:38:02.328: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.328: Closing device 135s (process:4026): libfprint-egismoc-DEBUG: 03:38:02.328: Cancel 135s (process:4026): libfprint-device-DEBUG: 03:38:02.328: Device reported close completion 135s (process:4026): libfprint-device-DEBUG: 03:38:02.328: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 135s (process:4026): libfprint-device-DEBUG: 03:38:02.329: 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 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 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 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 8, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 9, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 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 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 10, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 11, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 12, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 13, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 14, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 15, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 16, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 17, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 18, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 19, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d6b7e68e740 (FpiDeviceEgisMoc at 0x3a9c32e0)>, 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:4022): DEBUG: 03:38:02.342: umockdev.vala:154: Removing test bed /tmp/umockdev.TAYK22 135s (umockdev-run:4022): GLib-DEBUG: 03:38:02.348: 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/fp-device.test 135s TAP version 14 135s # random seed: R02S09705c2b0bff6d69e974c993357864bd 135s 1..17 135s # Start of device tests 135s # Start of async tests 135s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 135s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 135s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 135s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 135s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 135s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 135s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-C9G512/virtual_image.socket 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 (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:02.365: 82172651: ../libfprint/drivers/virtual-image.c:216 135s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_device_connection-DEBUG: 03:38:02.365: 82172751: ../libfprint/drivers/virtual-device-listener.c:153 135s # libfprint-image_device-DEBUG: Image device open completed 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.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:02.465: 82273332: ../libfprint/drivers/virtual-image.c:244 135s # libfprint-image_device-DEBUG: Image device close completed 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.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 135s ok 1 /device/async/open 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 # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 135s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 135s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 135s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 135s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 135s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-85ND22/virtual_image.socket 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 (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:02.572: 82379647: ../libfprint/drivers/virtual-image.c:216 135s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_device_connection-DEBUG: 03:38:02.572: 82379688: ../libfprint/drivers/virtual-device-listener.c:153 135s # libfprint-image_device-DEBUG: Image device open completed 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.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:02.672: 82480161: ../libfprint/drivers/virtual-image.c:244 135s # libfprint-image_device-DEBUG: Image device close completed 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.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 135s ok 2 /device/async/close 135s # End of async tests 135s # Start of sync tests 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 # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 135s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 135s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 135s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 135s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 135s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-Y0IE22/virtual_image.socket 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 (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:02.777: 82585581: ../libfprint/drivers/virtual-image.c:216 135s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_device_connection-DEBUG: 03:38:02.778: 82585622: ../libfprint/drivers/virtual-device-listener.c:153 135s # libfprint-image_device-DEBUG: Image device open completed 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.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:02.878: 82686147: ../libfprint/drivers/virtual-image.c:244 136s # libfprint-image_device-DEBUG: Image device close completed 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.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 136s ok 3 /device/sync/open 136s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 136s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 136s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 136s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 136s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 136s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 136s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 136s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-36OL22/virtual_image.socket 136s # libfprint-context-DEBUG: created 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 (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:02.983: 82791537: ../libfprint/drivers/virtual-image.c:216 136s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_device_connection-DEBUG: 03:38:02.983: 82791572: ../libfprint/drivers/virtual-device-listener.c:153 136s # libfprint-image_device-DEBUG: Image device open completed 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.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:03.084: 82892097: ../libfprint/drivers/virtual-image.c:244 136s # libfprint-image_device-DEBUG: Image device close completed 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.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 136s ok 4 /device/sync/close 136s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 136s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 136s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 136s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 136s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 136s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 136s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 136s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-6JO412/virtual_image.socket 136s # libfprint-context-DEBUG: created 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 (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:03.189: 82997212: ../libfprint/drivers/virtual-image.c:216 136s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_device_connection-DEBUG: 03:38:03.189: 82997246: ../libfprint/drivers/virtual-device-listener.c:153 136s # libfprint-image_device-DEBUG: Image device open completed 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.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:03.290: 83097724: ../libfprint/drivers/virtual-image.c:244 136s # libfprint-image_device-DEBUG: Image device close completed 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.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 136s ok 5 /device/sync/get_driver 136s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 136s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 136s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 136s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 136s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 136s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 136s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 136s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-ZL7512/virtual_image.socket 136s # libfprint-context-DEBUG: created 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 (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:03.395: 83203557: ../libfprint/drivers/virtual-image.c:216 136s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_device_connection-DEBUG: 03:38:03.395: 83203592: ../libfprint/drivers/virtual-device-listener.c:153 136s # libfprint-image_device-DEBUG: Image device open completed 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.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:03.496: 83304057: ../libfprint/drivers/virtual-image.c:244 136s # libfprint-image_device-DEBUG: Image device close completed 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.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 136s ok 6 /device/sync/get_device_id 136s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 136s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 136s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 136s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 136s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 136s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 136s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 136s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-539A22/virtual_image.socket 136s # libfprint-context-DEBUG: created 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 (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:03.601: 83409235: ../libfprint/drivers/virtual-image.c:216 136s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_device_connection-DEBUG: 03:38:03.601: 83409277: ../libfprint/drivers/virtual-device-listener.c:153 136s # libfprint-image_device-DEBUG: Image device open completed 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.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:03.702: 83509757: ../libfprint/drivers/virtual-image.c:244 136s # libfprint-image_device-DEBUG: Image device close completed 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.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 136s ok 7 /device/sync/get_name 136s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 136s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 136s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 136s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 136s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 136s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 136s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 136s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-253H22/virtual_image.socket 136s # libfprint-context-DEBUG: created 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 (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:03.808: 83616484: ../libfprint/drivers/virtual-image.c:216 136s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_device_connection-DEBUG: 03:38:03.808: 83616523: ../libfprint/drivers/virtual-device-listener.c:153 136s # libfprint-image_device-DEBUG: Image device open completed 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.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:03.909: 83717228: ../libfprint/drivers/virtual-image.c:244 137s # libfprint-image_device-DEBUG: Image device close completed 137s # libfprint-device-DEBUG: Device reported close completion 137s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 137s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 137s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 137s ok 8 /device/sync/get_scan_type 137s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 137s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 137s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 137s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 137s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 137s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 137s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 137s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-S8P112/virtual_image.socket 137s # libfprint-context-DEBUG: created 137s # libfprint-device-DEBUG: Device reported probe completion 137s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 137s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 137s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:04.015: 83823320: ../libfprint/drivers/virtual-image.c:216 137s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_device_connection-DEBUG: 03:38:04.015: 83823386: ../libfprint/drivers/virtual-device-listener.c:153 137s # libfprint-image_device-DEBUG: Image device open completed 137s # libfprint-device-DEBUG: Device reported open completion 137s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 137s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 137s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:04.116: 83924066: ../libfprint/drivers/virtual-image.c:244 137s # libfprint-image_device-DEBUG: Image device close completed 137s # libfprint-device-DEBUG: Device reported close completion 137s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 137s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 137s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 137s ok 9 /device/sync/get_finger_status 137s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 137s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 137s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 137s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 137s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 137s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 137s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 137s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-LBK212/virtual_image.socket 137s # libfprint-context-DEBUG: created 137s # libfprint-device-DEBUG: Device reported probe completion 137s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 137s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 137s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:04.223: 84031329: ../libfprint/drivers/virtual-image.c:216 137s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_device_connection-DEBUG: 03:38:04.223: 84031400: ../libfprint/drivers/virtual-device-listener.c:153 137s # libfprint-image_device-DEBUG: Image device open completed 137s # libfprint-device-DEBUG: Device reported open completion 137s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 137s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 137s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:04.324: 84132112: ../libfprint/drivers/virtual-image.c:244 137s # libfprint-image_device-DEBUG: Image device close completed 137s # libfprint-device-DEBUG: Device reported close completion 137s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 137s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 137s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 137s ok 10 /device/sync/get_nr_enroll_stages 137s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 137s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 137s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 137s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 137s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 137s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 137s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 137s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-UPP912/virtual_image.socket 137s # libfprint-context-DEBUG: created 137s # libfprint-device-DEBUG: Device reported probe completion 137s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 137s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 137s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:04.430: 84237856: ../libfprint/drivers/virtual-image.c:216 137s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_device_connection-DEBUG: 03:38:04.430: 84237892: ../libfprint/drivers/virtual-device-listener.c:153 137s # libfprint-image_device-DEBUG: Image device open completed 137s # libfprint-device-DEBUG: Device reported open completion 137s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 137s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 137s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:04.530: 84338388: ../libfprint/drivers/virtual-image.c:244 137s # libfprint-image_device-DEBUG: Image device close completed 137s # libfprint-device-DEBUG: Device reported close completion 137s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 137s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 137s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 137s ok 11 /device/sync/supports_identify 137s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 137s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 137s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 137s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 137s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 137s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 137s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 137s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-4HAC22/virtual_image.socket 137s # libfprint-context-DEBUG: created 137s # libfprint-device-DEBUG: Device reported probe completion 137s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 137s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 137s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:04.636: 84444542: ../libfprint/drivers/virtual-image.c:216 137s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_device_connection-DEBUG: 03:38:04.636: 84444577: ../libfprint/drivers/virtual-device-listener.c:153 137s # libfprint-image_device-DEBUG: Image device open completed 137s # libfprint-device-DEBUG: Device reported open completion 137s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 137s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 137s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:04.737: 84545083: ../libfprint/drivers/virtual-image.c:244 137s # libfprint-image_device-DEBUG: Image device close completed 137s # libfprint-device-DEBUG: Device reported close completion 137s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 137s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 137s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 137s ok 12 /device/sync/supports_capture 137s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 137s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 137s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 137s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 137s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 137s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 137s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 137s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-81RI22/virtual_image.socket 137s # libfprint-context-DEBUG: created 137s # libfprint-device-DEBUG: Device reported probe completion 137s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 137s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 137s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:04.844: 84652166: ../libfprint/drivers/virtual-image.c:216 137s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_device_connection-DEBUG: 03:38:04.844: 84652205: ../libfprint/drivers/virtual-device-listener.c:153 137s # libfprint-image_device-DEBUG: Image device open completed 137s # libfprint-device-DEBUG: Device reported open completion 137s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 137s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 137s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:04.945: 84752701: ../libfprint/drivers/virtual-image.c:244 138s # libfprint-image_device-DEBUG: Image device close completed 138s # libfprint-device-DEBUG: Device reported close completion 138s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 138s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 138s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 138s ok 13 /device/sync/has_storage 138s # Start of open tests 138s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 138s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 138s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 138s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 138s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 138s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 138s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 138s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-0ND212/virtual_image.socket 138s # libfprint-context-DEBUG: created 138s # libfprint-device-DEBUG: Device reported probe completion 138s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 138s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 138s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:05.052: 84860386: ../libfprint/drivers/virtual-image.c:216 138s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_device_connection-DEBUG: 03:38:05.052: 84860422: ../libfprint/drivers/virtual-device-listener.c:153 138s # libfprint-image_device-DEBUG: Image device open completed 138s # libfprint-device-DEBUG: Device reported open completion 138s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 138s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 138s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:05.153: 84960887: ../libfprint/drivers/virtual-image.c:244 138s # libfprint-image_device-DEBUG: Image device close completed 138s # libfprint-device-DEBUG: Device reported close completion 138s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 138s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 138s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 138s ok 14 /device/sync/open/notify 138s # End of open tests 138s # Start of close tests 138s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 138s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 138s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 138s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 138s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 138s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 138s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 138s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-J2I312/virtual_image.socket 138s # libfprint-context-DEBUG: created 138s # libfprint-device-DEBUG: Device reported probe completion 138s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 138s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 138s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:05.258: 85066519: ../libfprint/drivers/virtual-image.c:216 138s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_device_connection-DEBUG: 03:38:05.258: 85066557: ../libfprint/drivers/virtual-device-listener.c:153 138s # libfprint-image_device-DEBUG: Image device open completed 138s # libfprint-device-DEBUG: Device reported open completion 138s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 138s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 138s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:05.359: 85167063: ../libfprint/drivers/virtual-image.c:244 138s # libfprint-image_device-DEBUG: Image device close completed 138s # libfprint-device-DEBUG: Device reported close completion 138s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 138s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 138s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 138s ok 15 /device/sync/close/notify 138s # End of close tests 138s # Start of identify tests 138s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 138s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 138s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 138s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 138s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 138s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 138s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 138s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-LHL812/virtual_image.socket 138s # libfprint-context-DEBUG: created 138s # libfprint-device-DEBUG: Device reported probe completion 138s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 138s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 138s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:05.465: 85272637: ../libfprint/drivers/virtual-image.c:216 138s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_device_connection-DEBUG: 03:38:05.465: 85272678: ../libfprint/drivers/virtual-device-listener.c:153 138s # libfprint-image_device-DEBUG: Image device open completed 138s # libfprint-device-DEBUG: Device reported open completion 138s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 138s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 138s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:05.565: 85373190: ../libfprint/drivers/virtual-image.c:244 138s # libfprint-image_device-DEBUG: Image device close completed 138s # libfprint-device-DEBUG: Device reported close completion 138s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 138s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 138s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 138s ok 16 /device/sync/identify/cancelled 138s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 138s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 138s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 138s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 138s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 138s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 138s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 138s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-DCSF22/virtual_image.socket 138s # libfprint-context-DEBUG: created 138s # libfprint-device-DEBUG: Device reported probe completion 138s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 138s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 138s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:05.671: 85478955: ../libfprint/drivers/virtual-image.c:216 138s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_device_connection-DEBUG: 03:38:05.671: 85479027: ../libfprint/drivers/virtual-device-listener.c:153 138s # libfprint-image_device-DEBUG: Image device open completed 138s # libfprint-device-DEBUG: Device reported open completion 138s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 138s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 138s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4032): libfprint-virtual_image-DEBUG: 03:38:05.772: 85579628: ../libfprint/drivers/virtual-image.c:244 138s # libfprint-image_device-DEBUG: Image device close completed 138s # libfprint-device-DEBUG: Device reported close completion 138s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 138s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 138s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 138s ok 17 /device/sync/identify/null-prints 138s # End of identify tests 138s # End of sync tests 138s # End of device tests 138s PASS: libfprint-2/fp-device.test 138s Running test: libfprint-2/driver-nb1010.test 138s ** (umockdev-run:4072): DEBUG: 03:38:05.909: umockdev.vala:127: Created udev test bed /tmp/umockdev.S88G22 138s ** (umockdev-run:4072): DEBUG: 03:38:05.910: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-7 138s ** (umockdev-run:4072): DEBUG: 03:38:05.913: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-7 (subsystem usb) 138s ** (umockdev-run:4072): DEBUG: 03:38:05.917: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.S88G22/dev/bus/usb/001/003 138s ** (umockdev-run:4072): DEBUG: 03:38:05.917: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1 138s ** (umockdev-run:4072): DEBUG: 03:38:05.921: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1 (subsystem usb) 138s ** (umockdev-run:4072): DEBUG: 03:38:05.924: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.S88G22/dev/bus/usb/001/001 138s ** (umockdev-run:4072): DEBUG: 03:38:05.924: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0 138s ** (umockdev-run:4072): DEBUG: 03:38:05.926: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0 (subsystem pci) 138s ** (umockdev-run:4072): DEBUG: 03:38:05.929: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:01.3 138s ** (umockdev-run:4072): DEBUG: 03:38:05.930: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:01.3 (subsystem pci) 138s (umockdev-run:4072): GLib-GIO-DEBUG: 03:38:05.933: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 139s (process:4076): libfprint-context-DEBUG: 03:38:06.023: Initializing FpContext (libfprint version 1.94.8+tod1) 139s (process:4076): libfprint-tod-DEBUG: 03:38:06.024: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 139s (process:4076): libfprint-context-DEBUG: 03:38:06.026: No driver found for USB device 1D6B:0002 139s (process:4076): libfprint-device-DEBUG: 03:38:06.026: Device reported probe completion 139s (process:4076): libfprint-device-DEBUG: 03:38:06.026: Completing action FPI_DEVICE_ACTION_PROBE in idle! 139s (process:4076): libfprint-device-DEBUG: 03:38:06.026: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 139s (process:4076): libfprint-image_device-DEBUG: 03:38:06.028: Image device open completed 139s (process:4076): libfprint-device-DEBUG: 03:38:06.028: Device reported open completion 139s (process:4076): libfprint-nb1010-DEBUG: 03:38:06.028: nb1010 Initialized 139s (process:4076): libfprint-device-DEBUG: 03:38:06.028: Completing action FPI_DEVICE_ACTION_OPEN in idle! 139s (process:4076): libfprint-device-DEBUG: 03:38:06.028: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 139s (process:4076): libfprint-device-DEBUG: 03:38:06.028: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 139s (process:4076): libfprint-image_device-DEBUG: 03:38:06.028: Activating image device 139s (process:4076): libfprint-image_device-DEBUG: 03:38:06.028: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 139s (process:4076): libfprint-image_device-DEBUG: 03:38:06.028: Image device activation completed 139s (process:4076): libfprint-image_device-DEBUG: 03:38:06.028: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 139s (process:4076): libfprint-image_device-DEBUG: 03:38:06.028: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 139s (process:4076): libfprint-SSM-DEBUG: 03:38:06.028: [nb1010] M_LOOP_NUM_STATES entering state 0 139s (process:4076): libfprint-device-DEBUG: 03:38:06.028: Device reported finger status change: FP_FINGER_STATUS_NEEDED 139s (process:4076): libfprint-nb1010-DEBUG: 03:38:06.028: nb1010 Activated 139s (process:4076): libfprint-SSM-DEBUG: 03:38:06.078: [nb1010] M_LOOP_NUM_STATES entering state 1 139s (process:4076): libfprint-SSM-DEBUG: 03:38:06.078: [nb1010] M_LOOP_NUM_STATES entering state 2 139s (process:4076): libfprint-SSM-DEBUG: 03:38:06.079: [nb1010] M_LOOP_NUM_STATES entering state 3 139s (process:4076): libfprint-device-DEBUG: 03:38:06.079: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 139s (process:4076): libfprint-image_device-DEBUG: 03:38:06.079: Image device reported finger status: on 139s (process:4076): libfprint-image_device-DEBUG: 03:38:06.079: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 139s (process:4076): libfprint-SSM-DEBUG: 03:38:06.080: [nb1010] M_LOOP_NUM_STATES entering state 4 139s (process:4076): libfprint-SSM-DEBUG: 03:38:06.081: [nb1010] M_LOOP_NUM_STATES entering state 5 139s (process:4076): libfprint-device-DEBUG: 03:38:06.129: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 139s (process:4076): libfprint-SSM-DEBUG: 03:38:06.159: [nb1010] M_LOOP_NUM_STATES entering state 6 139s (process:4076): libfprint-image_device-DEBUG: 03:38:06.159: Image device captured an image 139s (process:4076): libfprint-image_device-DEBUG: 03:38:06.160: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 139s (process:4076): libfprint-device-DEBUG: 03:38:06.160: Device reported finger status change: FP_FINGER_STATUS_PRESENT 139s (process:4076): libfprint-SSM-DEBUG: 03:38:06.160: [nb1010] M_LOOP_NUM_STATES completed successfully 139s (process:4076): libfprint-nb1010-DEBUG: 03:38:06.160: nb1010 ssm complete cb 139s (process:4076): libfprint-device-DEBUG: 03:38:06.160: Device reported finger status change: FP_FINGER_STATUS_NONE 139s (process:4076): libfprint-image_device-DEBUG: 03:38:06.160: Image device reported finger status: off 139s (process:4076): libfprint-image_device-DEBUG: 03:38:06.160: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 139s (process:4076): libfprint-image_device-DEBUG: 03:38:06.160: Deactivating image device 139s (process:4076): libfprint-image_device-DEBUG: 03:38:06.160: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 139s (process:4076): libfprint-image_device-DEBUG: 03:38:06.160: Image device deactivation completed 139s (process:4076): libfprint-image_device-DEBUG: 03:38:06.160: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 139s (process:4076): libfprint-nb1010-DEBUG: 03:38:06.160: nb1010 Deactivated 139s (process:4076): libfprint-image-DEBUG: 03:38:06.176: Minutiae scan completed in 0.016711 secs 139s (process:4076): libfprint-device-DEBUG: 03:38:06.177: Device reported capture completion 139s (process:4076): libfprint-device-DEBUG: 03:38:06.177: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 139s (process:4076): libfprint-device-DEBUG: 03:38:06.177: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 139s (process:4076): libfprint-image_device-DEBUG: 03:38:06.177: Image device close completed 139s (process:4076): libfprint-device-DEBUG: 03:38:06.177: Device reported close completion 139s (process:4076): libfprint-nb1010-DEBUG: 03:38:06.177: nb1010 Deinitialized 139s (process:4076): libfprint-device-DEBUG: 03:38:06.177: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 139s (process:4076): libfprint-device-DEBUG: 03:38:06.177: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 139s Executing: libfprint-2/driver-nb1010.test 139s ** (umockdev-run:4072): DEBUG: 03:38:06.275: umockdev.vala:154: Removing test bed /tmp/umockdev.S88G22 139s (umockdev-run:4072): GLib-DEBUG: 03:38:06.282: unsetenv() is not thread-safe and should not be used after threads are created 139s Comparing PNGs /tmp/libfprint-umockdev-test-e19e9rmx/capture.png and /usr/share/installed-tests/libfprint-2/nb1010/capture.png 139s PASS: libfprint-2/driver-nb1010.test 139s Running test: libfprint-2/driver-uru4000-4500.test 139s ** (umockdev-run:4085): DEBUG: 03:38:06.342: umockdev.vala:127: Created udev test bed /tmp/umockdev.HUU512 139s ** (umockdev-run:4085): DEBUG: 03:38:06.343: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10 139s ** (umockdev-run:4085): DEBUG: 03:38:06.344: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb) 139s ** (umockdev-run:4085): DEBUG: 03:38:06.347: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.HUU512/dev/bus/usb/001/050 139s ** (umockdev-run:4085): DEBUG: 03:38:06.347: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 139s ** (umockdev-run:4085): DEBUG: 03:38:06.348: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 139s ** (umockdev-run:4085): DEBUG: 03:38:06.350: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.HUU512/dev/bus/usb/001/001 139s ** (umockdev-run:4085): DEBUG: 03:38:06.350: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 139s ** (umockdev-run:4085): DEBUG: 03:38:06.351: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 139s (process:4089): libfprint-context-DEBUG: 03:38:06.435: Initializing FpContext (libfprint version 1.94.8+tod1) 139s (process:4089): libfprint-tod-DEBUG: 03:38:06.435: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 139s (process:4089): libfprint-context-DEBUG: 03:38:06.437: No driver found for USB device 1D6B:0002 139s (process:4089): libfprint-device-DEBUG: 03:38:06.437: Device reported probe completion 139s (process:4089): libfprint-device-DEBUG: 03:38:06.437: Completing action FPI_DEVICE_ACTION_PROBE in idle! 139s (process:4089): libfprint-device-DEBUG: 03:38:06.438: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 139s (process:4089): GLib-DEBUG: 03:38:06.439: setenv()/putenv() are not thread-safe and should not be used after threads are created 139s (process:4089): libfprint-image_device-DEBUG: 03:38:06.447: Image device open completed 139s (process:4089): libfprint-device-DEBUG: 03:38:06.447: Device reported open completion 139s (process:4089): libfprint-device-DEBUG: 03:38:06.447: Completing action FPI_DEVICE_ACTION_OPEN in idle! 139s (process:4089): libfprint-device-DEBUG: 03:38:06.447: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 139s (process:4089): libfprint-device-DEBUG: 03:38:06.447: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 139s (process:4089): libfprint-image_device-DEBUG: 03:38:06.447: Activating image device 139s (process:4089): libfprint-image_device-DEBUG: 03:38:06.447: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 139s (process:4089): libfprint-SSM-DEBUG: 03:38:06.448: [uru4000] INIT_NUM_STATES entering state 0 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.448: read 1 regs at 7 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.449: reg value 1 139s (process:4089): libfprint-SSM-DEBUG: 03:38:06.449: [uru4000] INIT_NUM_STATES entering state 1 139s (process:4089): libfprint-SSM-DEBUG: 03:38:06.449: [uru4000] INIT_NUM_STATES entering state 3 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.449: set 81 139s (process:4089): libfprint-SSM-DEBUG: 03:38:06.449: [uru4000] INIT_NUM_STATES entering state 4 139s (process:4089): libfprint-SSM-DEBUG: 03:38:06.449: [uru4000] POWERUP_NUM_STATES entering state 0 139s (process:4089): libfprint-SSM-DEBUG: 03:38:06.450: [uru4000] POWERUP_NUM_STATES entering state 1 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.450: set 01 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.450: recv irq type 56aa 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.451: early scanpwr interrupt 139s (process:4089): libfprint-SSM-DEBUG: 03:38:06.451: [uru4000] POWERUP_NUM_STATES entering state 2 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.451: read 1 regs at 7 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.451: reg value 1 139s (process:4089): libfprint-SSM-DEBUG: 03:38:06.451: [uru4000] POWERUP_NUM_STATES entering state 3 139s (process:4089): libfprint-SSM-DEBUG: 03:38:06.451: [uru4000] POWERUP_NUM_STATES completed successfully 139s (process:4089): libfprint-SSM-DEBUG: 03:38:06.451: [uru4000] INIT_NUM_STATES entering state 5 139s (process:4089): libfprint-SSM-DEBUG: 03:38:06.451: [uru4000] INIT_NUM_STATES entering state 6 139s (process:4089): libfprint-SSM-DEBUG: 03:38:06.451: [uru4000] INIT_NUM_STATES entering state 7 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.451: read 16 regs at f0 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.452: reg value 1a 139s (process:4089): libfprint-SSM-DEBUG: 03:38:06.452: [uru4000] INIT_NUM_STATES entering state 8 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.452: Versions 0010 and 0115 139s (process:4089): libfprint-SSM-DEBUG: 03:38:06.452: [uru4000] INIT_NUM_STATES completed successfully 139s (process:4089): libfprint-image_device-DEBUG: 03:38:06.452: Image device activation completed 139s (process:4089): libfprint-image_device-DEBUG: 03:38:06.452: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 139s (process:4089): libfprint-image_device-DEBUG: 03:38:06.452: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.452: wait finger on 139s (process:4089): libfprint-device-DEBUG: 03:38:06.453: Device reported finger status change: FP_FINGER_STATUS_NEEDED 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.454: recv irq type 56aa 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.454: recv irq type 56aa 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.455: recv irq type 0101 139s (process:4089): libfprint-device-DEBUG: 03:38:06.455: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 139s (process:4089): libfprint-image_device-DEBUG: 03:38:06.455: Image device reported finger status: on 139s (process:4089): libfprint-image_device-DEBUG: 03:38:06.455: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.455: starting capture 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.455: Image encryption seed: 1374298404 139s (process:4089): libfprint-SSM-DEBUG: 03:38:06.455: [uru4000] IMAGING_NUM_STATES entering state 0 139s (process:4089): libfprint-SSM-DEBUG: 03:38:06.456: [uru4000] IMAGING_NUM_STATES entering state 1 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.457: hw header lines 289 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.457: dev2: 11240 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.457: image seems to be encrypted 139s (process:4089): libfprint-SSM-DEBUG: 03:38:06.457: [uru4000] IMAGING_NUM_STATES entering state 2 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.457: read 4 regs at 34 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.458: reg value f2 139s (process:4089): libfprint-SSM-DEBUG: 03:38:06.458: [uru4000] IMAGING_NUM_STATES entering state 3 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.458: encryption id 00 -> key 544409d6 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.458: 0 02 72 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.458: decoding 72 lines 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.458: 1 00 1 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.458: skipping 1 lines 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.458: 2 02 49 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.458: decoding 49 lines 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.458: 3 01 1 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.458: skipping 1 lines 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.458: 4 00 1 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.458: skipping 1 lines 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.458: 5 02 49 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.458: decoding 49 lines 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.458: 6 00 1 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.458: skipping 1 lines 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.458: 7 02 116 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.458: decoding 116 lines 139s (process:4089): libfprint-SSM-DEBUG: 03:38:06.459: [uru4000] IMAGING_NUM_STATES entering state 4 139s (process:4089): libfprint-image_device-DEBUG: 03:38:06.459: Image device captured an image 139s (process:4089): libfprint-image_device-DEBUG: 03:38:06.459: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 139s (process:4089): libfprint-device-DEBUG: 03:38:06.459: Device reported finger status change: FP_FINGER_STATUS_PRESENT 139s (process:4089): libfprint-SSM-DEBUG: 03:38:06.459: [uru4000] IMAGING_NUM_STATES completed successfully 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.459: await finger off 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.461: recv irq type 0200 139s (process:4089): libfprint-device-DEBUG: 03:38:06.461: Device reported finger status change: FP_FINGER_STATUS_NONE 139s (process:4089): libfprint-image_device-DEBUG: 03:38:06.461: Image device reported finger status: off 139s (process:4089): libfprint-image_device-DEBUG: 03:38:06.461: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 139s (process:4089): libfprint-image_device-DEBUG: 03:38:06.461: Deactivating image device 139s (process:4089): libfprint-image_device-DEBUG: 03:38:06.461: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.461: deactivating 139s (process:4089): libfprint-uru4000-DEBUG: 03:38:06.462: cancelled 139s (process:4089): libfprint-image_device-DEBUG: 03:38:06.462: Image device deactivation completed 139s (process:4089): libfprint-image_device-DEBUG: 03:38:06.462: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 139s (process:4089): libfprint-image-DEBUG: 03:38:06.482: Minutiae scan completed in 0.022695 secs 139s (process:4089): libfprint-device-DEBUG: 03:38:06.482: Device reported capture completion 139s (process:4089): libfprint-device-DEBUG: 03:38:06.482: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 139s (process:4089): libfprint-device-DEBUG: 03:38:06.482: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 139s (process:4089): libfprint-image_device-DEBUG: 03:38:06.483: Image device close completed 139s (process:4089): libfprint-device-DEBUG: 03:38:06.483: Device reported close completion 139s (process:4089): libfprint-device-DEBUG: 03:38:06.484: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 139s (process:4089): libfprint-device-DEBUG: 03:38:06.484: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 139s ** (umockdev-run:4085): DEBUG: 03:38:06.694: umockdev.vala:154: Removing test bed /tmp/umockdev.HUU512 139s (umockdev-run:4085): GLib-DEBUG: 03:38:06.699: unsetenv() is not thread-safe and should not be used after threads are created 139s Comparing PNGs /tmp/libfprint-umockdev-test-osktq06l/capture.png and /usr/share/installed-tests/libfprint-2/uru4000-4500/capture.png 139s PASS: libfprint-2/driver-uru4000-4500.test 139s Running test: libfprint-2/driver-vfs7552.test 139s ** (umockdev-run:4098): DEBUG: 03:38:06.781: umockdev.vala:127: Created udev test bed /tmp/umockdev.IFQE22 139s ** (umockdev-run:4098): DEBUG: 03:38:06.781: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-7 139s ** (umockdev-run:4098): DEBUG: 03:38:06.783: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-7 (subsystem usb) 139s ** (umockdev-run:4098): DEBUG: 03:38:06.786: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.IFQE22/dev/bus/usb/001/003 139s ** (umockdev-run:4098): DEBUG: 03:38:06.786: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 139s ** (umockdev-run:4098): DEBUG: 03:38:06.787: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 139s ** (umockdev-run:4098): DEBUG: 03:38:06.789: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.IFQE22/dev/bus/usb/001/001 139s ** (umockdev-run:4098): DEBUG: 03:38:06.790: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 139s ** (umockdev-run:4098): DEBUG: 03:38:06.790: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 139s (umockdev-run:4098): GLib-GIO-DEBUG: 03:38:06.793: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 139s (process:4102): libfprint-context-DEBUG: 03:38:06.896: Initializing FpContext (libfprint version 1.94.8+tod1) 139s (process:4102): libfprint-tod-DEBUG: 03:38:06.896: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 139s (process:4102): libfprint-context-DEBUG: 03:38:06.898: No driver found for USB device 1D6B:0002 139s (process:4102): libfprint-device-DEBUG: 03:38:06.898: Device reported probe completion 139s (process:4102): libfprint-device-DEBUG: 03:38:06.898: Completing action FPI_DEVICE_ACTION_PROBE in idle! 139s (process:4102): libfprint-device-DEBUG: 03:38:06.898: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.900: [vfs7552] DEV_OPEN_NUM_STATES entering state 0 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.900: [vfs7552] DEVICE OPEN entering state 0 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.900: Sending vfs7552_cmd_01 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.901: [vfs7552] DEVICE OPEN entering state 1 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.901: Receiving 64 bytes 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.901: Got 38 bytes out of 64 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.901: [vfs7552] DEVICE OPEN entering state 2 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.901: Sending vfs7552_cmd_19 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.902: [vfs7552] DEVICE OPEN entering state 3 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.902: Receiving 128 bytes 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.903: Got 68 bytes out of 128 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.903: [vfs7552] DEVICE OPEN entering state 4 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.903: Sending vfs7552_init_00 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.903: [vfs7552] DEVICE OPEN entering state 5 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.903: Receiving 64 bytes 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.904: [vfs7552] DEVICE OPEN entering state 6 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.904: Sending vfs7552_init_01 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.905: [vfs7552] DEVICE OPEN entering state 7 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.905: Receiving 64 bytes 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.905: [vfs7552] DEVICE OPEN entering state 8 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.905: Sending vfs7552_init_02 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.906: [vfs7552] DEVICE OPEN entering state 9 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.906: Receiving 64 bytes 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.907: [vfs7552] DEVICE OPEN entering state 10 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.907: Sending vfs7552_init_03 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.907: [vfs7552] DEVICE OPEN entering state 11 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.907: Receiving 64 bytes 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.912: Got 10 bytes out of 64 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.912: [vfs7552] DEVICE OPEN entering state 12 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.912: Sending vfs7552_init_04 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.912: [vfs7552] DEVICE OPEN entering state 13 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.912: Receiving 64 bytes 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.913: [vfs7552] DEVICE OPEN completed successfully 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.913: [vfs7552] DEV_OPEN_NUM_STATES completed successfully 139s (process:4102): libfprint-image_device-DEBUG: 03:38:06.913: Image device open completed 139s (process:4102): libfprint-device-DEBUG: 03:38:06.913: Device reported open completion 139s (process:4102): libfprint-device-DEBUG: 03:38:06.913: Completing action FPI_DEVICE_ACTION_OPEN in idle! 139s (process:4102): libfprint-device-DEBUG: 03:38:06.913: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 139s (process:4102): libfprint-device-DEBUG: 03:38:06.913: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 139s (process:4102): libfprint-image_device-DEBUG: 03:38:06.913: Activating image device 139s (process:4102): libfprint-image_device-DEBUG: 03:38:06.913: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 139s (process:4102): libfprint-image_device-DEBUG: 03:38:06.913: Image device activation completed 139s (process:4102): libfprint-image_device-DEBUG: 03:38:06.913: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 139s (process:4102): libfprint-image_device-DEBUG: 03:38:06.913: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 139s (process:4102): libfprint-device-DEBUG: 03:38:06.913: Device reported finger status change: FP_FINGER_STATUS_NEEDED 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.963: changing to 1 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.963: [vfs7552] ACTIVATE_NUM_STATES entering state 0 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.963: [vfs7552] ACTIVATE INIT entering state 0 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.963: Sending vfs7552_image_start 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.964: [vfs7552] ACTIVATE INIT entering state 1 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.964: Receiving 2048 bytes 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.964: Got 1962 bytes out of 2048 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.964: [vfs7552] ACTIVATE INIT completed successfully 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.964: [vfs7552] ACTIVATE_NUM_STATES entering state 1 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.965: [vfs7552] ACTIVATE INTERRUPT QUERY entering state 0 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.965: Receiving 8 bytes 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.965: Got 5 bytes out of 8 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.965: [vfs7552] ACTIVATE INTERRUPT QUERY completed successfully 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.965: [vfs7552] ACTIVATE_NUM_STATES entering state 2 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.965: [vfs7552] ACTIVATE_NUM_STATES entering state 1 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.965: [vfs7552] ACTIVATE INTERRUPT QUERY entering state 0 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.965: Receiving 8 bytes 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.966: Got 5 bytes out of 8 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.966: [vfs7552] ACTIVATE INTERRUPT QUERY completed successfully 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.966: [vfs7552] ACTIVATE_NUM_STATES entering state 2 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.966: [vfs7552] ACTIVATE_NUM_STATES entering state 3 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.966: [vfs7552] ACTIVATE_NUM_STATES completed successfully 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.966: [vfs7552] CAPTURE_NUM_STATES entering state 0 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.966: [vfs7552] QUERY DATA READY entering state 0 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.966: Sending vfs7552_is_image_ready 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.967: [vfs7552] QUERY DATA READY entering state 1 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.967: Receiving 64 bytes 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.967: Got 6 bytes out of 64 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.967: [vfs7552] QUERY DATA READY completed successfully 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.967: [vfs7552] CAPTURE_NUM_STATES entering state 1 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.967: [vfs7552] CAPTURE_NUM_STATES entering state 0 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.967: [vfs7552] QUERY DATA READY entering state 0 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.967: Sending vfs7552_is_image_ready 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.968: [vfs7552] QUERY DATA READY entering state 1 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.968: Receiving 64 bytes 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.968: Got 6 bytes out of 64 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.968: [vfs7552] QUERY DATA READY completed successfully 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.968: [vfs7552] CAPTURE_NUM_STATES entering state 1 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.968: [vfs7552] CAPTURE_NUM_STATES entering state 0 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.968: [vfs7552] QUERY DATA READY entering state 0 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.968: Sending vfs7552_is_image_ready 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.969: [vfs7552] QUERY DATA READY entering state 1 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.969: Receiving 64 bytes 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.970: Got 6 bytes out of 64 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.970: [vfs7552] QUERY DATA READY completed successfully 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.970: [vfs7552] CAPTURE_NUM_STATES entering state 1 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.970: [vfs7552] CAPTURE_NUM_STATES entering state 0 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.970: [vfs7552] QUERY DATA READY entering state 0 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.970: Sending vfs7552_is_image_ready 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.970: [vfs7552] QUERY DATA READY entering state 1 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.970: Receiving 64 bytes 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.971: Got 6 bytes out of 64 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.971: [vfs7552] QUERY DATA READY completed successfully 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.971: [vfs7552] CAPTURE_NUM_STATES entering state 1 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.971: [vfs7552] CAPTURE_NUM_STATES entering state 0 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.971: [vfs7552] QUERY DATA READY entering state 0 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.971: Sending vfs7552_is_image_ready 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.972: [vfs7552] QUERY DATA READY entering state 1 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.972: Receiving 64 bytes 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.972: Got 6 bytes out of 64 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.972: [vfs7552] QUERY DATA READY completed successfully 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.972: [vfs7552] CAPTURE_NUM_STATES entering state 1 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.972: [vfs7552] CAPTURE_NUM_STATES entering state 0 139s (process:4102): libfprint-SSM-DEBUG: 03:38:06.972: [vfs7552] QUERY DATA READY entering state 0 139s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.972: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.973: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.973: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.974: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.974: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.974: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.974: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.974: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.974: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.974: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.974: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.975: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.975: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.975: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.975: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.975: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.975: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.976: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.976: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.977: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.977: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.977: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.977: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.977: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.977: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.977: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.977: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.978: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.978: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.978: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.978: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.978: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.978: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.979: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.979: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.979: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.979: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.979: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.979: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.979: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.979: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.980: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.980: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.980: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.980: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.980: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.980: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.980: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.980: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.981: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.981: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.982: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.982: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.982: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.982: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.982: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.982: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.982: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.982: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.983: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.983: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.983: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.983: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.983: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.983: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.984: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.984: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.984: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.984: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.984: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.984: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.984: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.984: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.985: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.985: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.985: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.985: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.985: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.985: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.985: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.985: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.986: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.986: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.987: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.987: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.987: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.987: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.987: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.987: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.987: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.987: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.988: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.988: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.988: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.988: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.988: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.988: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.988: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.988: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.989: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.989: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.989: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.989: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.989: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.989: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.990: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.990: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.990: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.990: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.990: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.990: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.990: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.990: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.991: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.991: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.992: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.992: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.992: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.992: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.992: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.992: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.992: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.992: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.993: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.993: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.993: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.993: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.993: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.993: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.994: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.994: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.995: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.995: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.995: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.995: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.995: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.995: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.995: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.995: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.996: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.996: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.996: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.996: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.996: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.996: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.996: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.996: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.997: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.997: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.997: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.997: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.997: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.997: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.997: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.997: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.998: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.998: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.998: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.998: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.998: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.998: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.999: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.999: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.999: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.999: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.999: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.999: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:06.999: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:06.999: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.000: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.000: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.001: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.001: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.001: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.001: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.001: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.001: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.001: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.001: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.002: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.002: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.002: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.002: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.002: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.002: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.003: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.003: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.003: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.003: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.003: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.003: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.003: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.003: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.004: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.004: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.005: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.005: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.005: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.005: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.005: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.005: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.005: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.005: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.006: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.006: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.006: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.006: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.006: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.006: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.006: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.006: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.007: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.007: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.007: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.007: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.007: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.007: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.007: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.007: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.008: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.008: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.008: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.008: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.008: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.008: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.009: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.009: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.009: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.009: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.009: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.009: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.009: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.009: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.010: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.010: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.010: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.010: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.010: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.010: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.010: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.010: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.011: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.011: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.012: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.012: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.012: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.012: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.012: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.012: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.012: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.012: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.013: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.013: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.013: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.013: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.013: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.013: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.014: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.014: Receiving 64 bytes 140s (process:4102): libfprint-device-DEBUG: 03:38:07.014: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.014: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.014: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.014: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.014: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.014: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.014: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.015: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.015: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.016: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.016: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.016: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.016: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.016: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.016: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.016: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.016: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.017: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.017: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.017: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.017: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.017: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.017: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.018: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.018: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.018: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.018: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.018: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.018: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.018: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.018: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.019: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.019: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.019: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.019: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.019: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.019: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.019: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.019: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.020: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.020: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.021: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.021: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.021: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.021: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.021: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.021: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.021: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.021: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.022: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.022: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.022: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.022: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.022: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.022: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.022: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.022: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.023: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.023: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.023: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.023: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.023: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.023: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.024: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.024: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.025: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.025: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.025: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.025: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.025: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.025: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.025: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.025: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.026: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.026: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.026: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.026: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.026: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.026: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.027: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.027: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.027: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.027: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.027: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.027: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.027: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.027: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.028: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.028: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.028: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.028: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.028: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.028: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.028: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.028: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.029: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.029: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.030: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.030: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.030: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.030: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.030: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.030: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.030: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.030: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.031: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.031: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.031: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.031: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.031: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.031: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.032: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.032: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.032: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.032: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.032: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.032: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.032: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.032: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.033: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.033: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.033: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.033: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.033: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.033: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.033: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.033: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.034: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.034: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.035: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.035: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.035: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.035: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.035: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.035: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.036: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.036: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.036: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.036: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.036: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.036: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.036: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.036: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.037: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.037: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.038: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.038: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.038: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.038: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.038: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.038: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.038: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.038: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.039: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.039: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.039: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.039: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.039: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.039: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.040: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.040: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.040: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.040: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.040: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.040: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.040: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.040: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.041: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.041: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.042: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.042: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.042: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.042: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.042: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.042: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.042: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.042: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.043: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.043: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.043: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.043: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.043: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.043: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.043: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.043: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.044: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.044: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.044: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.044: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.044: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.044: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.044: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.044: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.045: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.045: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.045: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.045: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.045: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.045: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.046: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.046: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.046: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.046: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.046: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.047: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.047: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.047: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.047: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.047: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.048: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.048: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.048: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.048: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.048: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.048: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.048: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.048: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.049: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.049: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.049: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.049: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.049: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.049: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.050: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.050: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.050: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.050: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.050: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.050: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.050: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.050: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.051: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.051: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.051: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.051: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.051: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.051: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.051: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.051: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.052: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.052: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.053: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.053: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.053: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.053: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.053: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.053: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.053: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.053: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.054: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.054: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.054: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.054: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.054: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.054: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.054: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.054: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.055: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.055: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.055: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.055: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.055: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.055: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.055: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.055: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.056: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.056: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.056: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.056: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.056: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.056: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.056: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.056: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.057: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.057: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.057: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.057: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.057: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.057: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.057: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.057: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.058: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.058: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.058: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.058: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.058: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.058: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.059: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.059: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.059: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.059: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.059: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.059: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.059: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.059: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.060: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.060: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.060: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.060: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.060: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.060: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.060: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.060: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.061: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.061: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.062: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.062: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.062: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.062: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.062: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.062: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.062: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.062: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.063: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.063: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.063: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.063: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.063: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.063: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.063: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.063: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.064: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.064: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.064: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.064: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.064: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.064: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.064: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.064: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.065: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.065: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.065: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.065: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.065: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.065: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.065: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.065: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.066: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.066: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.066: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.066: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.066: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.066: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.066: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.066: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.067: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.067: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.067: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.067: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.067: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.067: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.068: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.068: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.068: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.068: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.068: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.068: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.068: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.068: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.069: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.069: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.069: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.069: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.069: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.069: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.069: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.069: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.070: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.070: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.070: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.070: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.070: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.070: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.070: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.070: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.071: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.071: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.071: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.071: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.071: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.071: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.071: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.071: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.072: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.072: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.072: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.072: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.072: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.072: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.072: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.072: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.073: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.073: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.073: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.073: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.073: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.073: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.073: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.073: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.074: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.074: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.075: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.075: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.075: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.075: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.075: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.075: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.075: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.075: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.076: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.076: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.076: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.076: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.076: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.076: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.076: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.076: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.077: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.077: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.077: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.077: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.077: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.077: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.077: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.077: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.078: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.078: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.078: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.078: [vfs7552] CAPTURE_NUM_STATES entering state 2 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.078: [vfs7552] REQUEST CHUNK entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.078: Sending vfs7552_read_image_chunk 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.078: [vfs7552] REQUEST CHUNK completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.078: [vfs7552] CAPTURE_NUM_STATES entering state 3 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.079: [vfs7552] CAPTURE_NUM_STATES entering state 2 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.079: [vfs7552] REQUEST CHUNK entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.079: Sending vfs7552_read_image_chunk 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.079: [vfs7552] REQUEST CHUNK completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.079: [vfs7552] CAPTURE_NUM_STATES entering state 3 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.080: [vfs7552] CAPTURE_NUM_STATES entering state 2 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.080: [vfs7552] REQUEST CHUNK entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.080: Sending vfs7552_read_image_chunk 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.081: [vfs7552] REQUEST CHUNK completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.081: [vfs7552] CAPTURE_NUM_STATES entering state 3 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.081: [vfs7552] CAPTURE_NUM_STATES entering state 4 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.081: variance_before = 396 140s 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.081: background stored 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.081: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.081: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.081: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.082: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.082: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.082: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.082: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.082: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.082: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.082: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.082: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.083: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.083: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.083: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.083: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.083: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.083: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.083: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.083: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.084: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.084: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.084: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.084: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.084: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.084: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.084: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.084: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.085: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.085: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.085: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.085: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.085: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.085: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.085: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.085: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.086: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.086: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.087: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.087: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.087: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.087: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.087: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.087: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.087: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.087: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.088: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.088: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.088: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.088: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.088: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.088: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.088: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.088: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.089: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.089: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.089: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.089: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.089: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.089: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.089: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.089: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.090: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.090: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.090: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.090: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.090: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.090: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.090: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.090: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.091: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.091: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.091: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.091: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.091: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.091: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.091: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.091: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.092: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.092: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.092: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.092: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.092: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.092: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.092: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.092: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.093: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.093: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.093: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.093: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.093: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.093: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.094: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.094: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.094: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.094: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.094: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.094: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.094: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.094: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.095: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.095: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.095: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.095: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.095: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.095: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.095: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.095: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.096: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.096: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.096: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.096: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.096: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.096: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.096: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.096: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.096: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.096: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.097: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.097: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.097: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.097: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.097: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.097: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.098: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.098: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.098: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.098: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.098: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.098: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.098: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.098: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.099: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.099: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.099: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.099: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.099: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.099: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.099: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.099: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.100: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.100: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.100: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.100: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.100: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.100: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.100: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.100: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.101: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.101: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.101: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.101: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.101: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.101: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.101: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.101: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.102: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.102: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.102: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.103: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.103: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.103: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.103: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.103: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.103: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.103: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.104: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.104: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.104: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.104: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.104: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.104: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.104: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.104: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.105: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.105: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.105: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.105: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.105: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.105: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.105: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.105: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.106: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.106: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.106: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.106: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.106: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.106: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.106: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.106: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.107: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.107: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.107: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.107: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.107: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.107: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.107: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.107: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.108: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.108: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.108: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.108: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.108: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.108: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.109: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.109: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.109: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.109: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.109: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.109: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.109: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.109: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.110: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.110: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.110: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.110: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.110: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.110: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.110: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.110: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.111: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.111: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.111: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.111: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.111: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.111: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.111: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.111: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.112: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.112: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.112: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.112: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.112: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.112: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.112: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.112: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.113: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.113: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.114: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.114: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.114: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.114: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.114: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.114: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.114: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.114: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.115: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.115: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.115: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.115: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.115: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.115: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.115: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.115: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.116: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.116: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.116: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.116: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.116: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.116: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.116: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.116: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.117: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.117: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.117: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.117: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.117: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.117: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.117: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.117: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.118: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.118: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.118: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.118: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.118: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.118: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.118: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.118: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.119: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.119: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.119: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.119: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.119: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.119: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.120: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.120: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.120: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.120: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.120: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.120: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.120: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.120: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.121: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.121: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.121: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.121: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.121: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.121: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.121: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.121: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.122: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.122: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.122: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.122: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.122: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.122: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.122: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.122: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.123: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.123: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.124: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.124: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.124: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.124: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.124: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.124: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.124: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.124: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.125: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.125: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.125: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.125: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.125: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.125: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.125: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.125: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.126: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.126: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.126: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.126: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.126: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.126: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.126: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.126: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.127: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.127: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.127: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.127: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.127: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.127: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.127: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.127: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.128: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.128: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.128: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.128: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.128: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.128: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.128: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.128: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.129: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.129: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.129: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.129: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.129: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.129: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.129: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.129: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.130: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.130: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.130: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.130: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.130: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.130: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.130: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.130: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.131: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.131: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.131: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.131: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.131: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.131: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.132: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.132: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.132: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.132: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.132: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.132: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.132: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.132: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.133: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.133: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.133: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.133: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.133: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.133: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.133: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.133: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.134: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.134: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.134: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.134: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.134: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.134: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.134: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.134: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.135: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.135: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.136: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.136: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.136: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.136: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.136: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.136: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.136: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.136: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.137: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.137: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.137: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.137: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.137: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.137: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.137: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.137: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.138: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.138: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.138: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.138: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.138: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.138: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.138: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.138: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.139: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.139: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.139: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.139: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.139: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.139: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.140: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.140: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.140: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.140: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.140: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.140: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.140: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.140: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.141: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.141: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.141: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.141: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.141: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.141: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.141: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.141: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.142: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.142: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.142: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.142: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.142: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.142: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.142: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.142: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.143: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.143: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.143: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.143: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.143: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.143: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.143: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.143: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.144: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.144: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.145: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.145: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.145: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.145: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.145: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.145: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.145: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.145: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.146: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.146: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.146: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.146: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.146: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.146: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.146: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.146: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.147: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.147: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.147: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.147: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.147: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.147: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.147: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.147: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.148: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.148: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.148: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.148: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.148: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.148: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.149: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.149: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.149: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.149: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.149: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.149: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.149: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.149: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.150: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.150: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.150: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.150: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.150: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.150: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.150: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.150: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.151: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.151: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.151: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.151: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.151: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.151: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.151: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.151: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.152: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.152: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.153: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.153: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.153: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.153: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.153: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.153: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.153: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.153: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.154: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.154: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.154: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.154: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.154: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.154: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.154: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.154: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.155: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.155: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.155: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.155: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.155: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.155: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.155: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.155: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.156: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.156: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.156: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.156: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.156: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.156: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.156: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.156: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.157: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.157: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.157: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.157: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.157: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.157: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.158: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.158: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.158: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.158: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.158: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.158: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.158: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.158: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.159: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.159: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.159: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.159: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.159: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.159: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.159: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.159: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.160: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.160: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.160: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.160: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.160: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.160: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.160: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.160: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.161: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.161: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.162: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.162: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.162: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.162: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.162: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.162: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.162: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.162: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.163: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.163: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.163: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.163: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.163: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.163: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.163: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.163: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.164: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.164: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.164: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.164: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.164: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.164: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.165: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.165: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.165: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.165: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.165: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.165: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.165: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.165: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.166: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.166: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.166: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.166: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.166: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.166: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.166: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.166: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.167: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.167: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.167: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.167: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.167: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.167: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.167: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.167: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.168: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.168: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.168: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.168: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.168: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.168: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.168: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.168: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.169: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.169: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.170: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.170: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.170: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.170: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.170: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.170: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.170: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.170: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.171: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.171: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.171: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.171: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.171: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.171: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.171: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.171: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.172: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.172: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.172: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.172: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.172: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.172: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.172: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.172: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.173: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.173: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.173: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.173: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.173: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.173: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.173: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.173: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.174: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.174: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.174: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.174: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.174: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.174: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.175: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.175: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.175: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.175: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.175: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.175: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.175: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.175: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.176: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.176: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.176: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.176: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.176: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.176: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.176: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.176: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.177: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.177: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.177: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.177: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.177: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.177: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.177: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.177: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.178: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.178: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.178: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.178: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.178: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.178: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.178: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.178: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.179: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.179: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.180: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.180: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.180: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.180: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.180: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.180: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.180: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.180: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.181: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.181: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.181: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.181: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.181: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.181: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.182: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.182: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.182: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.182: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.182: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.182: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.182: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.182: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.183: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.183: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.183: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.183: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.183: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.183: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.183: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.183: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.184: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.184: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.184: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.184: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.184: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.184: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.184: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.184: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.185: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.185: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.185: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.185: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.185: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.185: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.185: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.185: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.186: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.186: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.186: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.186: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.186: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.186: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.186: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.186: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.187: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.187: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.188: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.188: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.188: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.188: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.188: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.188: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.188: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.188: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.189: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.189: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.189: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.189: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.189: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.189: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.189: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.189: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.190: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.190: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.190: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.190: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.190: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.190: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.190: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.190: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.191: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.191: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.191: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.191: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.191: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.191: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.191: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.192: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.192: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.192: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.192: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.192: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.192: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.192: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.192: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.192: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.193: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.193: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.193: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.193: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.193: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.193: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.194: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.194: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.194: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.194: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.194: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.194: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.194: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.194: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.195: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.195: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.195: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.195: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.195: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.195: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.195: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.195: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.196: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.196: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.196: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.196: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.196: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.196: [vfs7552] CAPTURE_NUM_STATES entering state 2 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.196: [vfs7552] REQUEST CHUNK entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.196: Sending vfs7552_read_image_chunk 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.197: [vfs7552] REQUEST CHUNK completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.197: [vfs7552] CAPTURE_NUM_STATES entering state 3 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.198: [vfs7552] CAPTURE_NUM_STATES entering state 2 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.198: [vfs7552] REQUEST CHUNK entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.198: Sending vfs7552_read_image_chunk 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.198: [vfs7552] REQUEST CHUNK completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.198: [vfs7552] CAPTURE_NUM_STATES entering state 3 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.199: [vfs7552] CAPTURE_NUM_STATES entering state 2 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.199: [vfs7552] REQUEST CHUNK entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.199: Sending vfs7552_read_image_chunk 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.199: [vfs7552] REQUEST CHUNK completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.199: [vfs7552] CAPTURE_NUM_STATES entering state 3 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.200: [vfs7552] CAPTURE_NUM_STATES entering state 4 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.200: Cleaning image 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.200: variance_after = 20 140s 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.200: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.200: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.200: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.201: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.201: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.201: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.201: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.201: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.201: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.201: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.201: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.202: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.202: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.202: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.202: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.202: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.202: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.202: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.202: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.203: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.203: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.204: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.204: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.204: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.204: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.204: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.204: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.204: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.204: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.205: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.205: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.205: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.205: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.205: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.205: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.205: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.205: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.206: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.206: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.206: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.206: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.206: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.206: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.206: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.206: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.207: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.207: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.207: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.207: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.207: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.207: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.208: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.208: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.208: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.208: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.208: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.208: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.208: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.208: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.209: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.209: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.209: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.209: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.209: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.209: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.209: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.209: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.210: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.210: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.212: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.212: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.212: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.212: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.212: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.212: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.215: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.215: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.216: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.216: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.216: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.216: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.216: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.216: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.220: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.220: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.220: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.220: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.220: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.220: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.220: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.221: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.221: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.221: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.222: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.222: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.222: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.222: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.222: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.222: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.222: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.222: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.223: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.223: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.223: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.223: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.223: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.223: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.224: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.224: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.224: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.224: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.224: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.224: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.224: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.224: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.227: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.227: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.231: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.231: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.231: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.231: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.231: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.231: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.232: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.232: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.233: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.233: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.233: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.233: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.233: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.233: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.233: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.233: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.234: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.234: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.234: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.234: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.234: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.234: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.235: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.235: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.235: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.235: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.236: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.236: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.236: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.236: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.236: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.236: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.237: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.237: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.237: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.237: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.237: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.237: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.237: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.237: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.238: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.238: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.238: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.238: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.238: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.238: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.239: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.239: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.239: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.239: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.239: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.239: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.239: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.239: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.240: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.240: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.241: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.241: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.241: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.241: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.241: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.241: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.241: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.241: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.242: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.242: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.242: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.242: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.242: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.242: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.242: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.242: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.243: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.243: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.243: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.243: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.243: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.243: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.243: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.243: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.244: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.244: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.244: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.244: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.244: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.244: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.245: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.245: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.245: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.246: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.246: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.246: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.246: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.246: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.246: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.246: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.247: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.247: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.247: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.247: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.247: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.247: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.248: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.248: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.248: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.248: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.248: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.248: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.248: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.248: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.249: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.249: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.249: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.250: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.250: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.250: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.250: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.250: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.250: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.250: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.251: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.251: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.251: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.251: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.251: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.251: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.251: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.251: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.252: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.252: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.252: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.252: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.252: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.252: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.253: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.253: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.253: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.253: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.253: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.253: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.253: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.253: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.254: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.254: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.255: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.255: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.255: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.255: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.255: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.255: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.255: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.255: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.256: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.256: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.256: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.256: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.256: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.256: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.257: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.257: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.257: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.257: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.257: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.257: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.257: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.257: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.258: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.258: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.258: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.258: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.258: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.258: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.258: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.259: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.259: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.259: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.260: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.260: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.260: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.260: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.260: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.260: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.260: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.260: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.261: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.261: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.261: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.261: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.261: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.261: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.262: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.262: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.263: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.263: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.263: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.263: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.263: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.263: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.264: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.264: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.267: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.267: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.267: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.267: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.267: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.267: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.268: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.268: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.268: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.268: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.268: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.268: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.268: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.268: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.269: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.269: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.269: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.269: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.269: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.269: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.269: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.269: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.270: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.270: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.271: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.271: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.271: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.271: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.271: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.271: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.271: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.271: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.272: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.272: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.272: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.272: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.272: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.272: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.272: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.272: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.273: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.273: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.273: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.273: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.273: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.273: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.274: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.274: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.274: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.274: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.274: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.274: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.274: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.274: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.276: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.276: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.276: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.276: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.276: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.276: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.276: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.276: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.277: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.277: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.278: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.278: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.278: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.278: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.278: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.278: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.278: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.278: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.279: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.279: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.279: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.279: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.279: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.279: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.279: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.279: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.280: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.280: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.280: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.280: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.280: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.280: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.280: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.280: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.281: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.281: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.281: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.281: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.281: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.281: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.282: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.282: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.282: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.282: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.282: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.282: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.282: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.282: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.284: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.284: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.284: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.284: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.284: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.284: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.284: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.284: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.285: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.285: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.288: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.288: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.288: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.288: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.288: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.288: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.288: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.288: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.289: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.289: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.289: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.289: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.289: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.289: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.289: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.289: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.290: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.290: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.290: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.290: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.290: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.290: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.290: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.291: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.291: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.291: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.291: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.291: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.291: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.291: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.292: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.292: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.292: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.292: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.292: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.292: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.292: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.292: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.293: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.293: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.293: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.293: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.293: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.293: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.293: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.293: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.294: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.294: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.295: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.295: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.295: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.295: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.295: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.295: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.295: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.295: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.296: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.296: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.296: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.296: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.296: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.296: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.296: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.296: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.297: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.297: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.297: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.297: [vfs7552] CAPTURE_NUM_STATES entering state 2 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.297: [vfs7552] REQUEST CHUNK entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.297: Sending vfs7552_read_image_chunk 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.297: [vfs7552] REQUEST CHUNK completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.297: [vfs7552] CAPTURE_NUM_STATES entering state 3 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.298: [vfs7552] CAPTURE_NUM_STATES entering state 2 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.298: [vfs7552] REQUEST CHUNK entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.298: Sending vfs7552_read_image_chunk 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.298: [vfs7552] REQUEST CHUNK completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.299: [vfs7552] CAPTURE_NUM_STATES entering state 3 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.299: [vfs7552] CAPTURE_NUM_STATES entering state 2 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.299: [vfs7552] REQUEST CHUNK entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.299: Sending vfs7552_read_image_chunk 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.300: [vfs7552] REQUEST CHUNK completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.300: [vfs7552] CAPTURE_NUM_STATES entering state 3 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.300: [vfs7552] CAPTURE_NUM_STATES entering state 4 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.300: Cleaning image 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.300: variance_after = 18 140s 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.300: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.300: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.300: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.301: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.301: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.301: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.301: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.302: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.302: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.302: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.302: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.302: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.302: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.303: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.303: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.303: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.303: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.303: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.303: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.303: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.303: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.304: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.304: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.304: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.304: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.304: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.304: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.308: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.308: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.310: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.310: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.310: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.310: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.310: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.310: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.311: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.311: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.311: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.311: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.311: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.311: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.311: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.311: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.312: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.312: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.313: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.313: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.313: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.313: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.313: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.313: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.313: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.313: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.314: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.314: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.314: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.314: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.314: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.314: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.315: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.315: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.315: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.315: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.315: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.315: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.315: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.315: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.316: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.316: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.317: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.317: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.317: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.317: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.317: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.317: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.318: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.318: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.319: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.319: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.319: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.319: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.319: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.319: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.319: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.319: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.320: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.320: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.320: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.320: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.320: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.320: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.320: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.320: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.321: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.321: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.321: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.321: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.321: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.321: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.322: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.322: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.322: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.322: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.322: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.322: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.322: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.323: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.323: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.323: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.324: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.324: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.324: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.324: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.324: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.324: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.325: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.325: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.325: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.325: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.325: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.325: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.325: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.325: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.326: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.326: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.327: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.327: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.327: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.327: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.327: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.327: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.327: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.327: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.328: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.328: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.328: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.328: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.328: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.328: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.329: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.329: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.329: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.329: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.329: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.329: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.329: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.329: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.330: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.330: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.330: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.330: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.330: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.330: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.330: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.330: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.331: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.331: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.332: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.332: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.332: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.332: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.332: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.332: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.332: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.332: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.333: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.333: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.333: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.333: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.333: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.333: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.335: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.335: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.335: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.335: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.335: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.335: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.335: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.335: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.336: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.336: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.336: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.336: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.336: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.336: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.336: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.336: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.337: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.337: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.337: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.337: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.338: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.338: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.338: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.338: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.338: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.338: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.339: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.339: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.339: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.339: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.339: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.339: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.339: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.339: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.340: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.340: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.340: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.340: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.340: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.340: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.342: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.343: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.343: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.343: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.343: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.343: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.343: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.343: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.344: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.344: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.344: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.344: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.344: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.344: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.344: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.344: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.345: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.345: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.345: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.345: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.345: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.345: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.345: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.345: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.346: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.346: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.346: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.346: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.346: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.346: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.346: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.346: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.347: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.347: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.348: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.348: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.348: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.348: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.348: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.348: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.348: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.348: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.349: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.349: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.349: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.349: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.349: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.349: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.349: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.349: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.350: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.350: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.350: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.350: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.350: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.350: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.350: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.350: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.351: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.351: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.351: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.351: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.351: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.351: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.351: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.351: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.352: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.352: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.352: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.352: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.352: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.352: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.353: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.353: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.353: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.353: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.353: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.353: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.353: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.353: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.354: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.354: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.355: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.355: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.355: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.355: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.355: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.355: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.356: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.356: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.356: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.356: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.356: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.356: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.356: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.356: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.357: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.357: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.358: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.358: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.358: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.358: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.358: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.358: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.359: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.359: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.359: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.359: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.359: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.359: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.359: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.359: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.360: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.360: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.362: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.362: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.362: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.362: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.362: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.362: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.362: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.362: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.363: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.363: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.363: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.363: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.363: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.363: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.363: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.363: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.364: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.364: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.364: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.364: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.364: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.364: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.365: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.365: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.365: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.365: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.365: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.365: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.365: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.365: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.366: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.366: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.366: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.366: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.366: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.366: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.366: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.366: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.367: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.367: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.367: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.367: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.367: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.367: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.367: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.367: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.369: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.369: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.369: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.369: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.369: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.369: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.369: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.369: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.370: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.370: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.370: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.370: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.370: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.370: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.370: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.370: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.371: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.371: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.371: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.371: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.371: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.371: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.371: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.371: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.372: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.372: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.372: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.372: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.372: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.372: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.372: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.372: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.373: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.373: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.374: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.374: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.374: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.374: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.374: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.374: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.374: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.374: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.375: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.375: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.375: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.375: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.375: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.375: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.375: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.375: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.376: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.376: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.376: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.376: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.376: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.376: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.376: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.376: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.377: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.377: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.377: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.377: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.377: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.377: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.378: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.378: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.378: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.378: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.378: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.378: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.378: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.378: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.379: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.379: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.379: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.379: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.379: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.379: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.379: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.379: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.380: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.380: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.384: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.384: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.384: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.384: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.384: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.384: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.385: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.385: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.385: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.385: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.385: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.385: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.385: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.385: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.386: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.386: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.386: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.386: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.386: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.386: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.386: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.386: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.387: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.387: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.387: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.387: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.387: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.387: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.387: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.387: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.388: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.388: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.388: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.388: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.388: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.388: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.388: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.389: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.391: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.391: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.392: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.392: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.392: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.392: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.392: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.392: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.393: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.393: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.393: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.393: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.393: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.393: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.393: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.393: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.394: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.394: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.394: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.394: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.394: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.394: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.394: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.394: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.396: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.396: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.398: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.398: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.398: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.398: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.398: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.398: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.399: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.399: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.399: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.399: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.399: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.399: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.399: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.399: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.400: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.400: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.403: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.403: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.403: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.403: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.403: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.403: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.403: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.403: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.405: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.405: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.405: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.405: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.405: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.405: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.407: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.407: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.408: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.408: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.408: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.408: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.408: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.408: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.408: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.408: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.409: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.409: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.409: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.409: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.409: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.409: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.411: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.411: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.415: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.415: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.415: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.415: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.415: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.415: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.415: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.415: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.416: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.416: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.416: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.416: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.416: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.416: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.417: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.417: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.417: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.417: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.417: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.417: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.417: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.417: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.418: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.418: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.418: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.418: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.418: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.418: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.418: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.418: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.419: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.419: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.419: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.419: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.419: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.419: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.419: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.419: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.424: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.424: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.425: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.425: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.425: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.425: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.425: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.425: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.425: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.425: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.426: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.426: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.426: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.426: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.426: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.426: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.426: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.426: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.427: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.427: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.427: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.427: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.427: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.427: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.427: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.427: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.428: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.428: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.428: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.428: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.428: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.428: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.429: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.429: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.429: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.429: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.429: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.429: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.429: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.429: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.430: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.430: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.430: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.430: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.430: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.430: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.430: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.430: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.431: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.431: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.431: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.431: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.431: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.431: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.431: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.431: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.435: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.435: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.435: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.435: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.435: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.435: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.435: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.435: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.436: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.436: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.436: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.436: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.436: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.436: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.436: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.436: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.437: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.437: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.438: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.438: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.438: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.438: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.438: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.438: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.438: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.438: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.439: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.439: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.439: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.439: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.439: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.439: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.440: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.440: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.440: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.440: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.440: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.440: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.440: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.440: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.442: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.442: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.443: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.443: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.443: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.443: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.443: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.443: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.444: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.444: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.444: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.444: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.444: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.444: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.444: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.444: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.445: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.445: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.446: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.446: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.446: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.446: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.446: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.446: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.446: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.446: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.447: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.447: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.447: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.447: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.447: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.447: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.447: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.447: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.448: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.448: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.448: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.448: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.448: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.448: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.449: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.449: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.452: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.452: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.452: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.452: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.452: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.452: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.452: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.452: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.453: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.453: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.453: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.453: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.453: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.453: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.453: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.453: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.456: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.456: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.456: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.456: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.456: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.456: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.456: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.456: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.457: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.457: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.457: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.457: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.457: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.457: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.460: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.460: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.460: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.460: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.460: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.460: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.460: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.460: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.461: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.461: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.461: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.461: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.461: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.461: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.461: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.461: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.462: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.462: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.463: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.463: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.463: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.463: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.463: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.463: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.464: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.464: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.465: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.465: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.465: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.465: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.465: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.465: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.465: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.465: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.466: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.466: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.466: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.466: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.466: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.466: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.466: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.466: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.467: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.467: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.467: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.467: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.467: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.467: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.468: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.468: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.468: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.468: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.468: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.468: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.468: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.468: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.469: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.469: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.469: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.469: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.469: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.469: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.469: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.469: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.470: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.470: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.470: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.470: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.470: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.470: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.470: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.470: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.471: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.471: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.471: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.471: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.472: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.472: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.472: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.472: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.476: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.476: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.476: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.476: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.476: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.476: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.476: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.476: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.477: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.477: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.478: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.478: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.478: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.478: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.478: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.478: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.478: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.478: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.479: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.479: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.479: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.479: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.479: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.479: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.480: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.480: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.480: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.480: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.480: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.480: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.480: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.480: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.481: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.481: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.481: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.481: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.481: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.481: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.481: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.481: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.482: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.482: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.483: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.483: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.483: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.483: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.483: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.483: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.484: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.484: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.485: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.485: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.485: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.485: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.485: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.485: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.485: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.485: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.486: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.486: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.486: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.486: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.486: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.486: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.486: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.486: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.487: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.487: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.487: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.487: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.487: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.487: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.487: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.487: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.492: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.492: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.492: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.492: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.492: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.492: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.493: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.493: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.496: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.496: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.496: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.496: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.496: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.496: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.497: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.497: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.498: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.498: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.498: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.498: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.498: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.498: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.498: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.498: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.499: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.499: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.499: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.499: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.499: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.499: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.499: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.499: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.504: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.504: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.504: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.504: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.504: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.504: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.508: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.508: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.512: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.512: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.512: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.512: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.512: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.512: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.513: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.513: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.513: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.513: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.513: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.513: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.513: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.513: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.514: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.514: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.515: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.515: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.515: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.515: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.515: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.515: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.515: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.515: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.516: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.516: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.516: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.516: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.516: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.516: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.517: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.517: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.517: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.517: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.517: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.517: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.517: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.517: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.518: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.518: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.518: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.518: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.518: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.518: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.518: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.518: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.519: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.519: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.519: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.519: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.519: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.519: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.519: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.519: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.524: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.524: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.527: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.527: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.527: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.527: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.527: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.527: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.527: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.527: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.528: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.528: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.528: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.528: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.528: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.528: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.529: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.529: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.529: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.529: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.529: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.529: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.529: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.529: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.530: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.530: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.530: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.530: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.530: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.530: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.530: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.530: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.531: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.531: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.532: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.532: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.532: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.532: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.532: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.532: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.532: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.532: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.533: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.533: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.533: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.533: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.533: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.533: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.540: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.540: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.540: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.540: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.540: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.540: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.540: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.540: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.541: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.541: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.542: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.542: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.542: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.542: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.542: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.542: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.542: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.542: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.543: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.543: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.543: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.543: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.543: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.543: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.543: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.543: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.544: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.544: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.544: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.544: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.544: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.544: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.545: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.545: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.545: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.545: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.545: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.545: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.545: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.545: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.546: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.546: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.546: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.546: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.546: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.546: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.546: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.546: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.547: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.547: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.547: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.547: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.547: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.548: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.548: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.548: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.550: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.550: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.552: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.552: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.552: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.552: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.552: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.552: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.552: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.552: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.553: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.553: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.553: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.553: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.553: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.553: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.553: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.553: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.554: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.554: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.554: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.554: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.554: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.554: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.555: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.555: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.555: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.555: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.555: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.555: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.555: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.555: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.556: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.556: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.556: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.556: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.556: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.556: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.556: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.556: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.557: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.557: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.557: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.558: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.558: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.558: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.558: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.558: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.558: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.558: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.559: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.559: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.559: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.559: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.559: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.559: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.560: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.560: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.560: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.560: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.560: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.560: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.560: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.560: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.561: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.561: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.561: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.561: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.561: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.561: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.562: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.562: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.562: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.562: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.563: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.563: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.563: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.563: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.563: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.563: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.563: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.563: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.564: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.564: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.564: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.564: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.564: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.564: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.564: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.564: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.565: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.565: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.565: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.565: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.565: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.565: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.565: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.565: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.566: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.566: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.566: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.566: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.566: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.566: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.566: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.566: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.567: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.567: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.567: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.567: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.567: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.567: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.568: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.568: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.568: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.568: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.568: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.568: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.568: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.568: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.569: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.569: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.569: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.569: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.569: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.569: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.569: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.569: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.570: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.570: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.571: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.571: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.571: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.571: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.571: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.571: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.571: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.571: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.572: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.572: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.572: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.572: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.572: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.572: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.576: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.576: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.576: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.576: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.576: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.576: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.576: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.576: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.577: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.577: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.577: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.577: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.577: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.577: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.577: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.577: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.578: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.578: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.579: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.579: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.579: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.579: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.579: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.579: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.579: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.579: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.580: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.580: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.580: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.580: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.580: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.580: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.580: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.580: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.581: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.581: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.581: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.581: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.581: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.581: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.581: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.581: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.582: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.582: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.582: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.582: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.582: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.582: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.582: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.583: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.583: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.583: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.583: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.583: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.583: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.583: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.584: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.584: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.584: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.584: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.584: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.584: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.584: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.584: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.585: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.585: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.585: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.585: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.585: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.585: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.585: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.585: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.586: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.586: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.587: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.587: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.587: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.587: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.587: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.587: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.588: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.588: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.588: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.588: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.588: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.588: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.588: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.588: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.589: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.589: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.589: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.589: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.589: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.589: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.589: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.589: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.590: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.590: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.591: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.591: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.591: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.591: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.591: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.591: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.591: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.591: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.592: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.592: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.592: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.592: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.592: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.592: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.596: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.596: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.596: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.596: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.596: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.596: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.596: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.596: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.597: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.597: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.599: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.599: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.599: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.599: [vfs7552] CAPTURE_NUM_STATES entering state 2 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.599: [vfs7552] REQUEST CHUNK entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.599: Sending vfs7552_read_image_chunk 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.600: [vfs7552] REQUEST CHUNK completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.600: [vfs7552] CAPTURE_NUM_STATES entering state 3 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.603: [vfs7552] CAPTURE_NUM_STATES entering state 2 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.603: [vfs7552] REQUEST CHUNK entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.603: Sending vfs7552_read_image_chunk 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.604: [vfs7552] REQUEST CHUNK completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.604: [vfs7552] CAPTURE_NUM_STATES entering state 3 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.604: [vfs7552] CAPTURE_NUM_STATES entering state 2 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.604: [vfs7552] REQUEST CHUNK entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.604: Sending vfs7552_read_image_chunk 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.606: [vfs7552] REQUEST CHUNK completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.606: [vfs7552] CAPTURE_NUM_STATES entering state 3 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.606: [vfs7552] CAPTURE_NUM_STATES entering state 4 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.606: Cleaning image 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.607: variance_after = 20 140s 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.607: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.607: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.607: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.607: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.607: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.608: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.608: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.608: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.608: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.608: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.608: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.608: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.608: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.609: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.609: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.609: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.609: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.609: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.609: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.610: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.610: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.610: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.610: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.610: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.610: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.610: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.610: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.611: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.611: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.611: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.611: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.611: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.611: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.611: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.611: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.612: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.612: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.615: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.615: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.615: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.615: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.615: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.615: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.616: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.616: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.616: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.616: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.616: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.616: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.616: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.616: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.617: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.617: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.618: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.618: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.618: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.618: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.618: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.618: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.618: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.618: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.619: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.619: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.619: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.619: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.619: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.619: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.620: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.620: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.620: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.620: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.620: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.620: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.620: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.620: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.621: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.621: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.621: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.621: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.621: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.621: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.621: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.621: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.622: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.622: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.623: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.623: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.623: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.623: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.623: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.623: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.624: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.624: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.624: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.624: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.624: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.624: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.624: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.624: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.625: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.625: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.626: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.626: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.626: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.626: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.626: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.626: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.626: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.626: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.627: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.627: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.627: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.627: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.627: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.627: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.628: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.628: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.628: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.628: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.628: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.628: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.628: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.628: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.629: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.629: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.629: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.629: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.629: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.629: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.629: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.629: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.630: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.630: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.631: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.631: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.631: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.631: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.631: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.631: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.631: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.631: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.632: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.632: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.632: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.632: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.632: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.632: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.632: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.632: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.633: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.633: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.633: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.633: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.633: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.633: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.634: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.634: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.634: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.634: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.634: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.634: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.634: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.634: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.635: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.635: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.636: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.636: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.636: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.636: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.636: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.636: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.636: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.636: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.637: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.637: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.637: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.637: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.637: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.637: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.640: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.640: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.640: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.640: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.641: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.641: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.641: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.641: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.641: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.641: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.642: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.642: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.642: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.642: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.642: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.642: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.642: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.642: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.644: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.644: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.644: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.644: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.644: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.644: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.645: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.645: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.645: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.645: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.645: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.645: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.645: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.645: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.646: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.646: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.646: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.646: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.646: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.646: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.646: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.646: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.647: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.647: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.648: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.648: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.648: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.648: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.648: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.648: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.648: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.648: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.649: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.649: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.649: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.649: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.649: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.649: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.649: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.649: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.650: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.650: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.650: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.650: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.650: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.650: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.651: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.651: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.651: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.651: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.651: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.651: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.651: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.651: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.652: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.652: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.653: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.653: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.653: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.653: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.653: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.653: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.656: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.656: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.660: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.660: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.660: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.660: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.660: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.660: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.660: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.660: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.661: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.661: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.661: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.661: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.661: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.661: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.664: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.664: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.664: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.664: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.664: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.664: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.665: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.665: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.665: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.665: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.666: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.666: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.666: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.666: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.666: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.666: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.667: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.667: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.667: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.667: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.667: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.667: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.667: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.667: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.668: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.668: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.672: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.672: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.672: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.672: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.672: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.672: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.673: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.673: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.674: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.674: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.674: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.674: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.674: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.674: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.674: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.674: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.675: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.675: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.675: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.675: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.675: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.675: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.676: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.676: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.676: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.676: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.676: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.676: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.676: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.676: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.677: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.677: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.678: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.678: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.678: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.678: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.678: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.678: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.678: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.678: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.680: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.680: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.680: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.680: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.680: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.680: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.680: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.680: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.681: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.681: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.681: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.681: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.681: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.681: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.682: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.682: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.682: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.682: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.682: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.682: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.682: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.682: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.683: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.683: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.684: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.684: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.684: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.684: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.684: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.684: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.684: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.684: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.685: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.685: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.685: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.685: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.685: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.685: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.686: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.686: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.686: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.686: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.686: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.686: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.686: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.686: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.687: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.687: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.687: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.687: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.687: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.687: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.687: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.687: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.688: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.688: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.688: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.688: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.688: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.688: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.688: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.688: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.689: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.689: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.690: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.690: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.690: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.690: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.690: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.690: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.690: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.690: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.691: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.691: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.691: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.691: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.691: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.691: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.691: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.691: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.692: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.692: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.692: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.692: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.692: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.692: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.693: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.693: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.693: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.693: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.693: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.693: [vfs7552] CAPTURE_NUM_STATES entering state 2 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.693: [vfs7552] REQUEST CHUNK entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.693: Sending vfs7552_read_image_chunk 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.694: [vfs7552] REQUEST CHUNK completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.694: [vfs7552] CAPTURE_NUM_STATES entering state 3 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.694: [vfs7552] CAPTURE_NUM_STATES entering state 2 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.694: [vfs7552] REQUEST CHUNK entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.695: Sending vfs7552_read_image_chunk 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.695: [vfs7552] REQUEST CHUNK completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.695: [vfs7552] CAPTURE_NUM_STATES entering state 3 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.696: [vfs7552] CAPTURE_NUM_STATES entering state 2 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.696: [vfs7552] REQUEST CHUNK entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.696: Sending vfs7552_read_image_chunk 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.700: [vfs7552] REQUEST CHUNK completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.700: [vfs7552] CAPTURE_NUM_STATES entering state 3 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.701: [vfs7552] CAPTURE_NUM_STATES entering state 4 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.701: Cleaning image 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.701: variance_after = 18 140s 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.701: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.701: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.701: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.701: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.701: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.702: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.702: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.702: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.702: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.702: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.702: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.704: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.704: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.704: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.704: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.704: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.704: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.704: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.704: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.708: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.708: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.712: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.712: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.712: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.712: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.712: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.712: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.713: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.713: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.713: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.713: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.713: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.713: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.713: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.713: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.714: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.714: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.715: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.715: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.715: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.715: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.715: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.715: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.715: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.715: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.716: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.716: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.716: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.716: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.716: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.716: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.717: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.717: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.717: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.717: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.717: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.717: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.717: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.717: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.718: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.718: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.718: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.718: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.718: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.718: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.718: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.718: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.719: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.719: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.724: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.724: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.724: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.724: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.724: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.724: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.724: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.724: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.725: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.725: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.725: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.725: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.725: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.725: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.726: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.726: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.726: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.726: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.726: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.726: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.726: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.726: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.727: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.727: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.728: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.728: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.728: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.728: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.728: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.728: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.728: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.728: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.729: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.729: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.729: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.729: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.729: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.729: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.729: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.729: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.730: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.730: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.730: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.730: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.730: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.730: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.730: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.730: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.731: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.731: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.731: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.731: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.731: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.731: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.731: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.731: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.732: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.732: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.732: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.732: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.732: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.732: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.733: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.733: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.733: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.733: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.733: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.733: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.733: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.733: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.736: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.736: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.740: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.740: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.740: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.740: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.740: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.740: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.741: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.741: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.741: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.741: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.741: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.741: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.741: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.741: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.743: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.743: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.744: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.744: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.744: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.744: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.744: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.744: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.745: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.745: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.745: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.745: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.745: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.745: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.745: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.745: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.746: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.746: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.746: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.746: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.746: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.746: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.746: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.746: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.747: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.747: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.748: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.748: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.748: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.748: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.748: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.748: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.748: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.748: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.749: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.749: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.749: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.749: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.749: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.749: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.750: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.750: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.750: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.750: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.750: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.750: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.750: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.750: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.751: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.751: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.751: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.751: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.751: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.751: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.751: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.751: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.752: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.752: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.753: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.753: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.753: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.753: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.753: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.753: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.753: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.753: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.754: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.754: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.754: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.754: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.754: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.754: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.755: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.755: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.755: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.755: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.755: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.755: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.755: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.755: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.756: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.756: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.757: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.757: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.757: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.757: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.757: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.757: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.758: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.758: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.758: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.758: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.758: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.758: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.758: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.758: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.759: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.759: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.760: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.760: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.760: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.760: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.760: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.760: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.760: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.760: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.761: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.761: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.761: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.761: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.761: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.761: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.761: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.761: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.768: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.768: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.768: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.768: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.768: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.768: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.769: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.769: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.769: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.769: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.769: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.769: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.769: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.769: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.770: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.770: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.770: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.770: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.770: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.770: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.770: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.770: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.771: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.771: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.772: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.772: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.772: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.772: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.772: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.772: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.772: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.772: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.773: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.773: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.773: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.773: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.773: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.773: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.773: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.773: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.774: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.774: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.774: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.774: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.774: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.774: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.774: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.774: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.775: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.775: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.775: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.775: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.775: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.775: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.776: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.776: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.776: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.776: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.776: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.776: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.776: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.776: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.777: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.777: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.777: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.777: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.777: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.777: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.777: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.777: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.778: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.778: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.778: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.779: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.779: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.779: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.779: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.779: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.779: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.779: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.780: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.780: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.780: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.780: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.780: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.780: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.781: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.781: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.782: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.782: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.782: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.782: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.782: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.782: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.782: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.782: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.783: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.783: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.783: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.783: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.783: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.783: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.784: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.784: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.785: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.785: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.785: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.785: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.785: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.785: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.785: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.785: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.786: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.786: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.786: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.786: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.786: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.786: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.786: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.786: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.787: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.787: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.787: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.787: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.787: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.787: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.788: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.788: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.788: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.788: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.788: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.788: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.788: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.788: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.789: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.789: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.790: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.790: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.790: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.790: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.790: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.790: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.791: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.791: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.793: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.793: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.793: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.793: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.793: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.793: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.795: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.795: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.796: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.796: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.796: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.796: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.796: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.796: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.797: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.797: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.797: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.797: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.797: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.797: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.797: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.797: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.798: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.798: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.799: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.799: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.799: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.799: [vfs7552] CAPTURE_NUM_STATES entering state 2 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.799: [vfs7552] REQUEST CHUNK entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.799: Sending vfs7552_read_image_chunk 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.800: [vfs7552] REQUEST CHUNK completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.800: [vfs7552] CAPTURE_NUM_STATES entering state 3 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.800: [vfs7552] CAPTURE_NUM_STATES entering state 2 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.800: [vfs7552] REQUEST CHUNK entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.800: Sending vfs7552_read_image_chunk 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.801: [vfs7552] REQUEST CHUNK completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.801: [vfs7552] CAPTURE_NUM_STATES entering state 3 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.801: [vfs7552] CAPTURE_NUM_STATES entering state 2 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.801: [vfs7552] REQUEST CHUNK entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.802: Sending vfs7552_read_image_chunk 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.802: [vfs7552] REQUEST CHUNK completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.802: [vfs7552] CAPTURE_NUM_STATES entering state 3 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.803: [vfs7552] CAPTURE_NUM_STATES entering state 4 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.803: Cleaning image 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.803: variance_after = 18 140s 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.803: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.803: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.803: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.803: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.804: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.804: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.804: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.804: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.804: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.804: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.804: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.805: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.805: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.806: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.806: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.806: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.806: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.806: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.806: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.806: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.806: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.807: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.807: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.807: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.807: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.807: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.807: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.808: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.808: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.809: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.809: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.809: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.809: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.809: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.809: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.809: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.810: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.810: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.810: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.810: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.810: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.810: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.810: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.811: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.811: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.811: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.811: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.811: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.811: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.811: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.811: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.812: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.812: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.813: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.813: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.813: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.813: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.813: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.813: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.813: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.813: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.814: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.814: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.814: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.814: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.814: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.814: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.814: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.815: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.815: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.815: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.815: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.815: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.815: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.815: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.816: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.816: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.816: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.816: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.816: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.816: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.816: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.816: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.817: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.817: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.817: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.817: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.817: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.817: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.817: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.817: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.818: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.818: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.819: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.819: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.819: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.819: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.819: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.819: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.819: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.819: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.820: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.820: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.820: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.820: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.820: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.820: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.820: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.820: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.822: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.822: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.822: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.822: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.822: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.822: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.822: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.822: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.823: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.823: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.823: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.823: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.823: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.823: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.824: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.824: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.825: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.825: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.825: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.825: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.825: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.825: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.826: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.826: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.826: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.826: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.826: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.826: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.826: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.826: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.827: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.827: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.827: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.827: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.827: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.827: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.827: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.827: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.829: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.829: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.830: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.830: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.830: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.830: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.830: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.830: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.830: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.830: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.831: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.831: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.831: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.831: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.831: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.831: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.831: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.831: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.832: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.832: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.832: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.832: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.832: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.832: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.832: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.832: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.833: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.833: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.833: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.833: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.833: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.833: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.833: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.833: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.834: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.834: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.834: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.834: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.834: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.834: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.835: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.835: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.835: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.835: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.835: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.835: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.835: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.835: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.836: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.836: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.836: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.836: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.836: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.836: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.836: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.836: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.837: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.837: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.837: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.837: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.837: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.837: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.837: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.837: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.838: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.838: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.839: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.839: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.839: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.839: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.839: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.839: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.839: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.839: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.840: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.840: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.840: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.840: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.840: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.840: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.840: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.840: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.841: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.841: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.841: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.841: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.841: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.841: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.841: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.841: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.842: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.842: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.842: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.842: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.842: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.842: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.843: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.843: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.843: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.843: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.843: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.843: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.843: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.843: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.844: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.844: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.844: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.844: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.844: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.844: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.844: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.844: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.848: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.848: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.849: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.849: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.849: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.849: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.849: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.849: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.849: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.849: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.850: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.850: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.850: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.850: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.850: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.850: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.851: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.851: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.851: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.851: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.851: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.851: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.851: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.851: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.852: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.852: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.852: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.852: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.852: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.852: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.852: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.852: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.853: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.853: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.854: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.854: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.854: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.854: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.854: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.854: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.854: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.854: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.855: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.855: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.855: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.855: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.855: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.855: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.855: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.855: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.856: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.856: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.856: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.856: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.856: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.856: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.856: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.857: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.857: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.857: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.857: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.857: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.857: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.857: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.858: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.858: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.858: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.858: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.858: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.858: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.858: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.858: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.859: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.859: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.860: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.860: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.860: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.860: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.860: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.860: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.864: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.864: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.865: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.865: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.865: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.865: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.865: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.865: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.865: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.866: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.866: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.866: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.866: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.866: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.866: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.866: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.867: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.867: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.867: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.867: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.867: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.867: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.867: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.867: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.868: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.868: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.868: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.868: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.868: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.868: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.868: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.868: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.869: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.869: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.870: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.870: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.870: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.870: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.870: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.870: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.870: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.870: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.871: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.871: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.871: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.871: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.871: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.871: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.871: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.871: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.872: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.872: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.872: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.872: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.872: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.872: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.872: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.872: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.873: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.873: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.873: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.873: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.873: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.873: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.873: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.873: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.874: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.874: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.874: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.874: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.874: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.874: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.874: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.874: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.875: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.875: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.875: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.875: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.875: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.875: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.876: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.876: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.879: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.879: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.879: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.879: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.879: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.879: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.880: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.880: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.880: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.880: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.880: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.880: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.880: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.880: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.881: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.881: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.881: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.881: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.881: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.881: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.881: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.881: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.882: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.882: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.883: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.883: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.883: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.883: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.883: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.883: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.883: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.883: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.884: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.884: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.884: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.884: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.884: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.884: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.884: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.884: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.885: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.885: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.885: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.885: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.885: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.885: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.886: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.886: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.886: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.886: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.886: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.886: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.886: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.886: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.887: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.887: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.887: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.887: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.887: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.887: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.887: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.887: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.890: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.890: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.891: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.891: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.891: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.891: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.891: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.891: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.891: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.891: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.892: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.892: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.892: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.892: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.892: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.892: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.893: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.893: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.893: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.893: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.893: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.893: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.893: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.893: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.894: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.894: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.894: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.894: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.894: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.894: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.894: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.894: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.895: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.895: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.896: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.896: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.896: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.896: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.896: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.896: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.896: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.896: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.897: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.897: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.897: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.897: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.897: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.897: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.897: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.897: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.898: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.898: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.898: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.898: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.898: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.898: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.898: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.898: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.899: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.899: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.899: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.899: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.899: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.899: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.899: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.900: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.900: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.900: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.900: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.900: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.900: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.900: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.901: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.901: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.902: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.902: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.902: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.902: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.902: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.902: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.902: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.902: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.903: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.903: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.903: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.903: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.903: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.903: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.903: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.903: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.904: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.904: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.904: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.904: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.904: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.904: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.905: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.905: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.905: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.905: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.905: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.905: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.905: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.905: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.906: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.906: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.906: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.906: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.906: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.906: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.906: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.906: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.907: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.907: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.907: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.907: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.907: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.907: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.907: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.907: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.908: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.908: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.909: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.909: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.909: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.909: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.909: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.909: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.909: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.909: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.910: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.910: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.910: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.910: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.910: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.910: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.910: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.910: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.911: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.911: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.911: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.911: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.911: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.911: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.911: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.911: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.912: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.912: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.912: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.912: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.912: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.912: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.913: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.913: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.913: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.913: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.913: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.913: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.913: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.913: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.914: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.914: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.914: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.914: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.914: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.914: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.914: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.914: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.915: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.915: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.915: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.915: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.915: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.915: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.915: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.915: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.916: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.916: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.916: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.916: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.916: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.917: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.917: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.917: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.917: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.917: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.918: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.918: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.918: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.918: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.918: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.918: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.918: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.918: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.919: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.919: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.919: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.919: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.919: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.919: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.919: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.919: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.920: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.920: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.920: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.920: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.920: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.920: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.920: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.921: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.921: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.921: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.921: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.921: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.921: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.921: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.922: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.922: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.922: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.922: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.922: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.922: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.922: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.922: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.923: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.923: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.923: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.923: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.923: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.923: [vfs7552] CAPTURE_NUM_STATES entering state 2 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.923: [vfs7552] REQUEST CHUNK entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.923: Sending vfs7552_read_image_chunk 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.924: [vfs7552] REQUEST CHUNK completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.924: [vfs7552] CAPTURE_NUM_STATES entering state 3 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.925: [vfs7552] CAPTURE_NUM_STATES entering state 2 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.925: [vfs7552] REQUEST CHUNK entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.925: Sending vfs7552_read_image_chunk 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.925: [vfs7552] REQUEST CHUNK completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.925: [vfs7552] CAPTURE_NUM_STATES entering state 3 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.926: [vfs7552] CAPTURE_NUM_STATES entering state 2 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.926: [vfs7552] REQUEST CHUNK entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.926: Sending vfs7552_read_image_chunk 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.927: [vfs7552] REQUEST CHUNK completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.927: [vfs7552] CAPTURE_NUM_STATES entering state 3 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.927: [vfs7552] CAPTURE_NUM_STATES entering state 4 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.927: Cleaning image 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.927: variance_after = 18 140s 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.927: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.927: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.927: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.928: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.928: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.932: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.932: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.932: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.932: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.932: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.932: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.933: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.933: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.933: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.933: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.933: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.933: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.933: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.933: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.934: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.934: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.934: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.935: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.935: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.935: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.935: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.935: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.935: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.935: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.936: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.936: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.936: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.936: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.936: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.936: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.936: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.936: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.937: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.937: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.937: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.937: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.937: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.937: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.938: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.938: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.938: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.938: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.938: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.938: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.938: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.938: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.939: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.939: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.940: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.940: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.940: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.940: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.940: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.940: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.940: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.940: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.941: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.941: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.941: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.941: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.941: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.941: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.941: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.941: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.942: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.942: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.942: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.942: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.942: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.942: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.942: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.942: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.943: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.943: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.943: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.943: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.943: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.943: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.943: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.943: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.944: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.944: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.944: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.944: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.944: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.944: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.945: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.945: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.946: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.946: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.946: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.946: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.946: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.946: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.947: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.947: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.947: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.947: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.947: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.947: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.947: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.947: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.948: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.948: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.948: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.949: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.949: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.949: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.949: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.949: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.949: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.949: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.950: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.950: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.950: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.950: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.950: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.950: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.950: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.950: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.951: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.951: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.951: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.951: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.951: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.951: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.951: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.951: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.952: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.952: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.952: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.952: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.952: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.952: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.952: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.952: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.953: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.953: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.953: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.953: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.953: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.953: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.953: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.953: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.954: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.954: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.954: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.954: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.954: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.954: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.955: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.955: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.955: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.955: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.955: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.955: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.955: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.955: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.957: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.957: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.958: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.958: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.958: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.958: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.958: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.958: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.958: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.958: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.959: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.959: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.959: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.959: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.959: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.959: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.959: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.959: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.960: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.960: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.960: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.960: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.960: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.960: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.960: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.960: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.961: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.961: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.961: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.961: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.961: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.961: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.961: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.961: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.962: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.962: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.962: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.962: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.962: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.962: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.962: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.962: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.963: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.963: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.963: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.963: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.963: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.963: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.964: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.964: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.964: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.964: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.964: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.964: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.964: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.964: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.965: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.965: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.965: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.965: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.965: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.965: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.965: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.965: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.966: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.966: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.966: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.966: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.966: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.966: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.966: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.966: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.967: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.967: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.967: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.968: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.968: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.968: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.968: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.968: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.968: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.968: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.969: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.969: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.969: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.969: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.969: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.969: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.969: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.969: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.970: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.970: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.970: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.970: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.970: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.970: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.970: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.970: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.971: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.971: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.971: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.971: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.971: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.971: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.971: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.971: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.972: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.972: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.972: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.972: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.972: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.972: Sending vfs7552_is_image_ready 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.972: [vfs7552] QUERY DATA READY entering state 1 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.972: Receiving 64 bytes 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.973: Got 6 bytes out of 64 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.973: [vfs7552] QUERY DATA READY completed successfully 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.973: [vfs7552] CAPTURE_NUM_STATES entering state 1 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.973: [vfs7552] CAPTURE_NUM_STATES entering state 0 140s (process:4102): libfprint-SSM-DEBUG: 03:38:07.973: [vfs7552] QUERY DATA READY entering state 0 140s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.973: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.973: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.974: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.974: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.974: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.974: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.974: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.974: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.974: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.974: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.975: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.975: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.975: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.975: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.975: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.975: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.975: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.975: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.976: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.976: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.976: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.976: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.976: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.976: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.976: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.977: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.977: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.977: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.977: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.977: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.977: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.977: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.977: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.978: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.978: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.978: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.978: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.978: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.978: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.978: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.978: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.979: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.979: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.979: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.979: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.980: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.980: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.980: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.980: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.980: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.980: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.981: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.981: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.981: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.981: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.981: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.981: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.981: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.981: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.982: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.982: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.982: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.982: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.982: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.982: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.982: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.982: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.983: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.983: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.983: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.983: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.983: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.983: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.983: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.983: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.984: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.984: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.984: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.984: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.984: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.984: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.984: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.985: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.985: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.985: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.985: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.985: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.985: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.985: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.986: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.986: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.986: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.986: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.986: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.986: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.986: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.986: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.987: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.987: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.987: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.987: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.987: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.987: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.987: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.987: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.988: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.988: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.988: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.988: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.988: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.988: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.988: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.988: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.989: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.989: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.989: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.989: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.989: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.989: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.989: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.989: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.990: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.990: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.991: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.991: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.991: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.991: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.991: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.991: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.991: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.991: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.992: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.992: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.992: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.992: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.992: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.992: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.992: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.992: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.993: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.993: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.993: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.993: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.993: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.993: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.993: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.993: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.994: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.994: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.994: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.994: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.994: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.994: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.994: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.994: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.995: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.995: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.995: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.995: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.995: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.995: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.995: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.995: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.996: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.996: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.996: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.996: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.996: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.996: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.997: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.997: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.997: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.997: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.997: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.997: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.997: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.997: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.998: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.998: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.998: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.998: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.998: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.998: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.998: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.998: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:07.999: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.999: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:07.999: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.000: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.000: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.000: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.000: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.000: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.000: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.000: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.001: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.001: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.001: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.001: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.001: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.001: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.003: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.003: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.003: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.003: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.003: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.003: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.003: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.003: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.004: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.004: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.004: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.004: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.004: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.004: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.004: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.004: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.005: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.005: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.005: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.005: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.005: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.005: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.005: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.005: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.006: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.006: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.006: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.006: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.006: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.006: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.006: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.006: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.007: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.007: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.008: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.008: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.008: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.008: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.008: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.008: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.012: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.012: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.013: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.013: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.013: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.013: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.013: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.013: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.014: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.014: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.014: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.014: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.014: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.014: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.014: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.014: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.015: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.015: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.015: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.015: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.015: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.015: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.015: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.015: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.017: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.017: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.017: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.017: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.017: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.017: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.017: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.017: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.018: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.018: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.019: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.019: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.019: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.019: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.019: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.019: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.019: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.019: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.020: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.020: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.020: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.020: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.020: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.020: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.020: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.020: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.021: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.021: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.021: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.021: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.021: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.021: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.022: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.022: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.022: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.022: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.022: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.022: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.022: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.022: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.023: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.023: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.023: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.023: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.023: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.023: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.023: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.023: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.024: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.024: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.025: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.025: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.025: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.025: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.025: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.025: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.025: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.025: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.026: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.026: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.026: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.026: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.026: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.026: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.026: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.026: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.027: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.027: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.027: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.027: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.027: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.027: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.028: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.028: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.028: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.028: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.028: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.028: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.028: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.028: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.029: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.029: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.029: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.029: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.029: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.029: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.029: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.029: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.030: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.030: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.030: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.030: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.030: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.030: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.030: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.030: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.031: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.031: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.032: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.032: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.032: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.032: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.032: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.032: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.032: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.032: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.033: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.033: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.033: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.033: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.033: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.033: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.033: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.033: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.034: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.034: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.034: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.034: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.034: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.034: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.034: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.034: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.035: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.035: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.035: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.035: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.035: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.035: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.035: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.036: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.036: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.036: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.036: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.036: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.036: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.036: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.037: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.037: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.037: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.037: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.037: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.037: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.037: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.037: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.038: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.038: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.038: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.038: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.038: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.038: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.038: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.038: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.039: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.039: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.039: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.039: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.039: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.039: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.039: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.039: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.040: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.040: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.040: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.040: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.040: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.040: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.040: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.040: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.041: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.041: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.041: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.041: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.041: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.041: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.041: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.041: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.042: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.042: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.043: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.043: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.043: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.043: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.043: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.043: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.043: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.043: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.044: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.044: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.044: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.044: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.044: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.044: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.045: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.045: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.045: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.045: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.045: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.045: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.045: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.045: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.046: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.046: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.046: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.046: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.046: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.046: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.046: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.046: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.047: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.047: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.047: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.047: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.047: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.047: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.047: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.047: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.048: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.048: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.049: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.049: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.049: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.049: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.049: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.049: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.049: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.049: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.050: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.050: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.050: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.050: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.050: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.050: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.050: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.050: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.051: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.051: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.051: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.051: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.051: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.051: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.052: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.052: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.052: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.052: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.052: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.052: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.052: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.052: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.053: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.053: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.053: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.053: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.053: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.053: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.053: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.053: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.054: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.054: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.054: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.054: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.054: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.055: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.055: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.055: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.055: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.055: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.056: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.056: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.056: [vfs7552] CAPTURE_NUM_STATES entering state 4 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.056: Cleaning image 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.056: variance_after = 18 141s 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.056: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.056: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.056: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.057: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.057: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.058: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.058: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.058: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.058: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.058: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.058: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.058: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.058: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.059: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.059: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.059: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.059: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.059: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.059: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.059: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.059: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.062: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.062: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.062: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.062: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.062: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.062: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.062: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.062: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.063: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.063: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.063: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.063: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.063: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.063: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.063: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.063: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.064: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.064: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.064: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.064: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.064: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.064: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.064: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.064: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.065: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.065: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.065: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.065: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.065: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.065: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.065: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.066: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.066: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.066: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.066: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.066: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.066: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.066: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.067: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.067: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.067: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.067: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.067: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.067: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.067: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.067: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.068: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.068: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.068: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.068: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.068: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.068: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.068: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.068: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.069: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.069: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.069: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.069: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.069: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.069: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.069: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.069: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.070: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.070: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.070: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.070: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.070: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.070: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.070: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.070: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.071: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.071: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.072: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.072: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.072: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.072: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.072: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.072: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.072: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.073: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.073: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.073: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.073: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.073: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.073: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.073: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.074: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.074: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.074: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.074: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.074: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.074: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.074: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.074: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.075: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.075: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.075: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.075: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.075: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.075: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.075: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.075: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.076: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.076: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.076: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.076: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.076: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.076: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.076: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.076: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.077: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.077: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.077: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.077: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.077: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.077: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.077: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.077: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.078: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.078: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.078: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.078: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.078: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.078: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.078: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.078: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.079: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.079: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.079: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.079: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.079: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.079: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.079: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.079: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.084: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.084: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.084: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.084: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.084: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.084: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.084: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.084: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.085: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.085: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.086: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.086: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.086: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.086: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.086: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.086: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.086: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.086: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.087: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.087: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.087: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.087: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.087: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.087: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.087: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.088: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.088: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.088: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.088: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.088: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.088: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.088: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.089: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.089: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.089: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.089: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.089: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.089: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.089: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.089: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.090: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.090: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.090: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.090: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.091: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.091: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.091: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.091: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.092: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.092: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.094: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.094: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.094: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.094: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.094: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.094: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.096: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.096: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.097: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.097: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.097: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.097: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.097: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.097: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.098: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.098: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.098: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.098: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.098: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.098: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.098: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.098: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.099: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.099: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.099: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.099: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.099: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.099: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.099: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.099: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.100: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.100: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.101: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.101: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.101: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.101: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.101: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.101: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.101: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.101: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.102: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.102: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.102: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.102: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.102: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.102: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.102: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.102: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.103: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.103: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.103: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.103: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.103: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.103: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.103: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.103: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.104: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.104: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.104: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.104: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.104: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.104: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.105: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.105: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.105: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.105: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.105: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.105: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.105: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.105: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.106: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.106: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.108: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.108: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.108: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.108: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.108: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.108: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.109: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.109: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.110: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.110: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.110: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.110: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.110: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.110: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.110: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.111: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.111: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.111: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.111: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.111: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.111: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.111: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.112: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.112: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.112: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.112: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.112: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.112: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.112: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.112: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.113: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.113: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.114: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.114: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.114: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.114: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.114: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.114: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.114: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.114: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.115: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.115: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.115: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.115: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.115: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.115: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.115: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.115: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.116: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.116: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.116: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.116: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.116: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.116: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.117: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.117: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.117: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.117: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.117: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.117: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.117: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.117: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.118: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.118: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.118: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.118: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.118: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.118: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.118: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.118: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.119: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.119: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.120: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.120: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.120: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.120: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.120: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.121: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.121: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.121: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.121: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.121: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.122: [vfs7552] CAPTURE_NUM_STATES entering state 4 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.122: Cleaning image 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.122: variance_after = 17 141s 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.122: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.122: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.122: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.123: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.123: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.123: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.123: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.123: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.123: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.123: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.123: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.124: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.124: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.125: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.125: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.125: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.125: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.125: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.125: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.126: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.126: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.126: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.126: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.126: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.126: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.126: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.126: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.127: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.127: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.127: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.127: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.127: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.127: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.127: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.127: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.128: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.128: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.129: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.129: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.129: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.129: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.129: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.129: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.129: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.129: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.130: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.130: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.130: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.130: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.130: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.130: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.130: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.130: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.131: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.131: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.131: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.131: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.131: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.131: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.132: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.132: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.132: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.132: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.132: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.132: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.132: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.132: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.133: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.133: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.133: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.133: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.133: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.133: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.133: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.133: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.134: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.134: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.134: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.134: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.134: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.134: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.134: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.134: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.135: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.135: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.135: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.135: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.135: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.135: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.135: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.135: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.136: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.136: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.136: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.136: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.136: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.136: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.136: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.136: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.137: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.137: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.137: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.137: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.137: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.137: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.137: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.137: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.138: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.138: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.138: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.138: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.138: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.138: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.139: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.139: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.139: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.139: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.140: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.140: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.140: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.140: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.140: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.140: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.140: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.140: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.141: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.141: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.141: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.141: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.141: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.141: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.141: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.141: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.142: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.142: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.142: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.142: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.142: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.142: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.142: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.143: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.143: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.143: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.143: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.143: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.143: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.143: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.143: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.144: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.144: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.144: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.144: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.144: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.144: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.144: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.145: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.145: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.145: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.145: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.145: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.145: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.145: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.145: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.146: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.146: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.146: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.146: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.146: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.146: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.146: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.146: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.147: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.147: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.147: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.147: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.147: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.147: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.147: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.147: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.148: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.148: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.150: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.150: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.150: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.150: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.150: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.150: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.151: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.151: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.151: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.151: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.151: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.151: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.151: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.151: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.152: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.152: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.152: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.152: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.152: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.152: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.152: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.152: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.153: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.153: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.153: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.153: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.153: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.153: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.153: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.153: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.154: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.154: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.154: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.154: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.154: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.154: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.154: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.154: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.155: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.155: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.155: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.155: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.155: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.155: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.155: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.155: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.156: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.156: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.157: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.157: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.157: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.157: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.157: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.157: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.157: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.157: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.158: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.158: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.158: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.158: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.158: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.158: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.158: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.158: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.159: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.159: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.159: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.159: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.159: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.159: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.159: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.159: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.160: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.160: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.160: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.160: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.160: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.160: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.161: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.161: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.161: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.161: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.161: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.161: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.161: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.161: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.162: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.162: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.162: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.162: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.162: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.162: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.162: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.162: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.163: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.163: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.163: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.163: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.163: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.163: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.163: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.163: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.164: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.164: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.164: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.164: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.165: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.165: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.165: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.165: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.165: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.165: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.165: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.166: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.166: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.166: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.166: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.166: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.166: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.166: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.166: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.167: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.167: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.167: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.167: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.167: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.167: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.167: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.168: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.168: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.168: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.168: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.168: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.168: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.169: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.169: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.170: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.170: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.170: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.170: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.170: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.170: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.170: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.170: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.171: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.171: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.171: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.171: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.171: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.171: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.172: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.172: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.172: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.172: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.172: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.172: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.172: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.172: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.173: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.173: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.173: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.173: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.173: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.173: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.173: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.174: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.174: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.174: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.175: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.175: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.175: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.175: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.175: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.176: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.176: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.176: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.176: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.176: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.177: [vfs7552] CAPTURE_NUM_STATES entering state 4 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.177: Cleaning image 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.177: variance_after = 16 141s 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.177: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.177: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.177: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.178: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.178: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.178: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.178: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.178: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.178: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.178: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.178: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.179: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.179: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.179: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.179: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.179: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.179: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.179: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.179: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.180: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.180: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.180: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.180: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.180: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.180: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.180: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.180: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.181: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.181: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.182: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.182: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.182: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.182: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.182: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.182: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.182: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.182: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.183: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.183: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.183: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.183: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.183: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.183: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.183: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.183: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.184: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.184: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.184: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.184: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.184: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.184: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.184: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.184: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.185: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.185: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.185: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.185: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.185: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.185: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.185: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.185: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.186: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.186: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.186: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.186: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.186: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.186: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.186: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.186: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.187: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.187: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.187: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.187: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.187: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.187: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.187: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.188: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.188: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.188: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.188: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.188: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.188: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.188: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.189: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.189: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.189: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.189: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.189: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.189: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.189: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.189: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.190: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.190: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.190: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.190: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.190: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.190: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.190: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.190: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.191: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.191: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.191: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.191: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.191: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.191: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.191: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.191: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.192: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.192: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.192: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.193: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.193: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.193: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.193: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.193: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.193: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.193: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.194: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.194: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.194: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.194: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.194: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.194: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.194: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.194: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.195: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.195: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.195: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.195: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.195: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.195: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.195: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.195: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.196: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.196: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.196: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.196: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.196: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.196: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.196: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.196: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.198: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.198: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.198: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.198: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.198: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.198: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.198: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.198: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.199: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.199: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.199: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.199: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.199: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.199: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.199: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.199: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.200: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.200: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.200: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.200: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.200: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.200: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.201: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.201: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.201: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.201: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.201: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.201: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.201: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.201: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.202: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.202: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.203: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.203: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.203: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.203: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.203: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.203: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.203: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.203: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.204: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.204: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.204: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.204: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.204: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.204: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.205: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.205: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.205: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.205: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.205: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.205: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.205: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.205: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.206: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.206: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.206: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.206: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.206: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.206: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.206: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.206: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.207: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.207: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.207: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.207: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.207: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.207: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.207: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.207: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.208: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.208: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.208: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.208: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.208: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.208: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.208: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.208: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.209: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.209: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.209: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.209: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.209: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.209: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.209: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.209: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.210: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.210: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.210: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.210: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.210: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.210: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.210: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.210: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.211: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.211: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.211: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.211: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.211: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.211: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.211: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.211: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.212: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.212: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.212: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.213: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.213: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.213: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.213: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.213: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.213: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.213: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.214: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.214: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.214: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.214: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.214: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.214: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.214: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.214: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.215: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.215: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.215: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.215: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.215: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.215: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.215: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.215: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.216: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.216: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.216: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.216: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.216: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.216: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.216: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.216: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.217: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.217: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.217: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.217: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.217: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.217: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.217: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.218: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.218: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.218: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.218: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.218: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.218: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.218: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.219: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.219: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.219: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.219: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.219: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.219: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.219: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.219: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.220: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.220: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.220: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.220: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.220: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.220: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.220: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.220: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.221: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.221: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.221: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.221: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.221: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.221: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.221: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.221: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.222: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.222: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.222: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.222: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.222: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.222: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.222: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.222: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.223: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.223: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.223: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.223: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.223: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.223: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.223: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.223: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.224: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.224: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.225: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.225: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.225: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.225: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.225: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.225: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.225: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.225: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.226: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.226: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.226: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.226: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.226: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.226: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.226: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.226: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.227: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.227: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.227: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.227: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.227: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.228: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.228: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.228: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.229: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.229: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.229: [vfs7552] CAPTURE_NUM_STATES entering state 4 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.229: Cleaning image 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.229: variance_after = 17 141s 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.229: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.229: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.229: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.230: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.230: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.231: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.231: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.231: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.231: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.231: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.231: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.231: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.231: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.232: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.232: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.232: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.232: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.232: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.232: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.232: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.232: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.233: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.233: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.233: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.233: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.233: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.233: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.233: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.233: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.234: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.234: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.234: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.234: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.234: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.234: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.234: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.234: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.235: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.235: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.235: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.235: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.235: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.235: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.235: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.235: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.236: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.236: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.236: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.236: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.236: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.236: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.237: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.237: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.237: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.238: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.238: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.238: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.238: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.238: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.238: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.238: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.239: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.239: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.239: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.239: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.239: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.239: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.239: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.240: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.240: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.240: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.240: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.240: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.240: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.240: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.241: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.241: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.241: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.241: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.241: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.241: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.241: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.241: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.242: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.242: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.243: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.243: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.243: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.243: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.243: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.243: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.243: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.243: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.244: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.244: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.244: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.244: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.244: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.244: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.244: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.244: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.245: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.245: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.245: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.245: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.245: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.245: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.245: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.245: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.246: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.246: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.246: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.246: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.246: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.246: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.246: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.247: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.247: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.247: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.247: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.247: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.247: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.247: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.248: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.248: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.248: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.248: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.248: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.248: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.248: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.248: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.249: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.249: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.249: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.250: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.250: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.250: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.250: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.250: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.250: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.250: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.251: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.251: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.251: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.251: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.251: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.251: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.251: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.251: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.252: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.252: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.252: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.252: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.252: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.252: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.252: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.252: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.253: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.253: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.253: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.253: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.253: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.253: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.253: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.254: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.254: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.254: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.254: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.254: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.254: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.254: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.255: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.255: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.255: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.255: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.255: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.255: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.255: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.255: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.256: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.256: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.256: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.256: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.256: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.256: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.256: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.256: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.257: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.257: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.257: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.257: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.257: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.257: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.257: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.257: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.258: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.258: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.258: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.258: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.258: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.258: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.259: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.259: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.259: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.259: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.260: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.260: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.260: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.260: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.260: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.260: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.260: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.260: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.261: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.261: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.261: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.261: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.261: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.261: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.261: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.261: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.262: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.262: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.262: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.262: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.262: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.262: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.263: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.263: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.263: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.263: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.263: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.263: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.263: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.263: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.264: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.264: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.264: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.264: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.264: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.264: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.264: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.264: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.265: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.265: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.265: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.265: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.265: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.265: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.265: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.265: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.266: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.266: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.266: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.266: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.266: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.266: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.266: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.266: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.267: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.267: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.267: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.267: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.267: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.267: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.267: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.268: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.268: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.268: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.268: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.268: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.268: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.268: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.268: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.268: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.269: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.269: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.270: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.270: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.270: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.270: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.270: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.270: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.271: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.271: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.271: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.271: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.271: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.271: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.271: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.271: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.272: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.272: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.272: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.272: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.272: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.272: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.272: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.272: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.273: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.273: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.273: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.274: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.274: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.274: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.274: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.274: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.274: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.274: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.275: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.275: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.275: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.275: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.275: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.275: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.275: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.275: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.276: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.276: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.276: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.276: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.276: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.276: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.276: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.276: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.277: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.277: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.277: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.277: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.277: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.277: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.277: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.277: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.278: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.278: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.278: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.278: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.278: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.278: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.278: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.278: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.279: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.279: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.279: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.279: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.279: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.279: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.279: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.280: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.280: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.280: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.280: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.280: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.280: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.280: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.281: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.281: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.281: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.281: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.281: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.281: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.281: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.281: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.282: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.282: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.282: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.282: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.282: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.282: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.282: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.282: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.283: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.283: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.283: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.283: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.283: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.283: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.283: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.283: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.284: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.284: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.284: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.284: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.284: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.284: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.284: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.284: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.285: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.285: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.286: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.286: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.286: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.288: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.288: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.288: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.288: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.288: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.289: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.289: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.290: [vfs7552] CAPTURE_NUM_STATES entering state 4 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.290: Cleaning image 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.290: variance_after = 17 141s 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.290: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.290: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.290: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.290: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.290: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.291: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.291: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.291: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.291: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.291: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.291: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.292: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.292: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.293: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.293: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.293: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.293: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.293: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.293: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.293: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.293: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.294: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.294: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.294: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.294: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.294: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.294: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.295: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.295: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.295: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.295: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.295: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.295: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.295: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.295: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.296: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.296: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.296: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.296: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.296: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.296: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.296: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.296: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.297: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.297: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.297: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.297: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.297: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.297: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.297: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.297: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.298: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.298: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.298: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.298: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.298: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.298: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.298: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.298: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.299: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.299: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.299: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.299: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.299: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.299: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.299: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.299: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.300: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.300: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.301: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.301: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.301: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.301: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.301: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.301: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.301: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.301: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.302: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.302: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.302: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.302: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.302: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.302: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.302: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.302: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.303: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.303: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.303: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.303: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.303: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.303: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.303: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.303: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.304: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.304: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.304: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.304: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.304: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.304: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.305: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.305: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.306: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.306: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.306: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.306: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.306: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.306: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.307: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.307: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.307: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.307: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.307: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.307: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.307: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.307: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.308: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.308: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.309: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.309: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.309: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.309: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.309: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.309: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.309: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.309: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.310: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.310: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.310: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.310: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.310: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.310: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.310: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.310: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.311: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.311: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.311: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.311: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.311: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.311: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.311: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.312: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.312: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.312: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.312: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.312: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.312: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.312: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.313: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.313: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.313: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.313: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.313: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.313: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.313: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.313: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.314: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.314: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.314: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.314: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.314: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.314: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.314: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.314: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.315: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.315: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.315: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.315: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.315: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.315: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.315: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.315: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.316: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.316: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.317: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.317: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.317: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.317: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.317: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.317: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.319: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.319: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.322: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.322: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.322: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.322: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.322: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.322: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.323: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.323: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.324: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.324: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.324: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.324: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.324: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.324: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.325: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.325: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.325: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.325: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.325: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.325: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.325: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.325: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.326: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.326: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.326: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.326: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.326: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.326: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.326: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.326: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.327: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.327: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.327: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.327: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.328: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.328: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.328: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.328: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.328: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.328: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.329: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.329: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.329: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.329: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.329: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.329: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.329: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.329: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.330: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.330: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.330: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.330: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.330: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.330: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.330: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.330: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.331: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.331: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.331: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.331: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.331: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.331: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.331: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.331: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.332: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.332: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.332: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.332: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.332: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.332: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.333: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.333: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.333: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.333: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.333: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.333: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.333: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.333: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.334: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.334: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.334: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.334: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.334: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.334: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.334: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.334: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.335: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.335: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.336: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.336: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.336: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.336: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.336: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.336: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.336: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.336: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.337: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.337: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.337: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.337: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.337: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.337: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.337: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.337: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.338: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.338: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.338: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.338: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.338: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.338: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.338: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.339: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.339: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.339: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.339: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.339: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.339: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.339: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.339: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.340: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.340: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.340: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.340: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.340: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.340: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.340: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.340: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.341: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.341: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.341: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.341: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.341: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.341: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.341: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.341: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.342: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.342: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.342: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.342: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.342: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.342: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.342: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.342: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.343: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.343: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.343: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.343: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.343: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.343: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.343: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.343: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.344: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.344: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.344: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.344: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.344: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.344: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.344: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.345: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.345: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.345: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.345: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.345: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.345: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.345: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.345: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.346: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.346: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.346: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.346: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.346: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.346: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.346: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.346: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.347: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.347: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.348: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.348: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.348: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.348: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.348: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.348: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.349: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.349: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.349: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.349: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.349: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.349: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.349: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.349: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.350: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.350: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.350: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.350: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.350: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.350: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.350: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.350: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.351: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.351: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.351: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.351: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.351: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.351: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.351: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.351: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.352: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.352: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.352: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.353: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.353: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.353: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.353: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.353: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.353: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.353: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.354: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.354: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.354: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.354: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.354: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.354: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.354: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.354: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.355: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.355: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.355: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.355: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.355: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.355: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.355: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.355: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.356: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.356: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.356: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.356: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.356: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.356: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.356: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.356: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.357: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.357: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.357: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.357: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.357: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.357: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.357: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.357: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.358: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.358: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.358: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.358: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.358: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.358: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.358: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.358: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.359: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.359: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.359: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.359: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.359: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.359: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.359: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.359: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.360: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.360: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.360: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.360: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.360: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.360: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.360: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.360: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.361: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.361: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.361: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.361: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.361: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.361: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.361: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.362: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.362: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.362: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.362: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.362: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.362: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.362: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.363: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.363: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.363: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.363: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.363: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.364: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.364: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.364: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.364: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.364: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.365: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.365: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.365: [vfs7552] CAPTURE_NUM_STATES entering state 4 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.365: Cleaning image 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.365: variance_after = 17 141s 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.365: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.365: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.365: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.366: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.366: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.366: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.366: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.366: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.367: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.367: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.367: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.367: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.367: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.368: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.368: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.368: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.368: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.368: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.368: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.368: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.368: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.369: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.369: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.369: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.369: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.369: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.369: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.369: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.369: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.370: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.370: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.370: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.370: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.370: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.370: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.371: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.371: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.371: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.371: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.371: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.371: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.371: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.371: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.372: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.372: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.372: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.372: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.372: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.372: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.372: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.372: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.373: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.373: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.373: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.373: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.373: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.373: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.373: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.373: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.374: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.374: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.374: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.374: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.374: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.374: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.374: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.374: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.375: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.375: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.375: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.375: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.375: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.375: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.375: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.375: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.376: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.376: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.376: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.376: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.376: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.376: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.376: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.376: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.377: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.377: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.378: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.378: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.378: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.378: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.378: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.378: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.378: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.378: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.379: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.379: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.379: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.379: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.379: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.379: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.379: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.379: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.380: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.380: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.380: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.380: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.380: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.380: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.380: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.380: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.381: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.381: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.381: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.381: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.381: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.381: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.381: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.381: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.382: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.382: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.382: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.382: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.382: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.382: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.382: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.382: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.383: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.383: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.383: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.383: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.383: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.383: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.383: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.383: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.384: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.384: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.384: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.384: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.384: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.384: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.384: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.384: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.385: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.385: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.385: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.385: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.385: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.385: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.386: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.386: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.386: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.386: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.386: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.386: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.386: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.386: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.387: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.387: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.388: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.388: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.388: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.388: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.388: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.388: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.389: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.389: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.389: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.389: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.389: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.389: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.389: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.389: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.390: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.390: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.390: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.390: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.390: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.390: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.390: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.390: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.391: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.391: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.392: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.392: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.392: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.392: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.392: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.392: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.392: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.392: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.393: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.393: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.393: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.393: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.393: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.393: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.393: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.394: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.394: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.394: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.394: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.394: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.394: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.394: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.395: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.395: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.395: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.395: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.395: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.395: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.395: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.395: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.396: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.396: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.396: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.396: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.396: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.396: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.396: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.396: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.397: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.397: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.397: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.397: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.397: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.397: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.397: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.397: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.398: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.398: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.398: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.398: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.398: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.398: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.398: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.398: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.399: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.399: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.400: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.400: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.400: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.400: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.400: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.400: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.400: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.400: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.401: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.401: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.401: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.401: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.401: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.401: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.401: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.401: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.402: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.402: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.402: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.402: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.402: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.402: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.402: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.402: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.403: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.403: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.403: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.403: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.403: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.403: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.403: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.403: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.405: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.405: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.405: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.405: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.405: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.405: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.405: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.405: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.406: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.406: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.406: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.406: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.406: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.406: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.406: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.406: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.407: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.407: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.407: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.407: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.407: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.407: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.407: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.407: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.408: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.408: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.408: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.408: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.408: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.408: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.408: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.408: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.409: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.409: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.409: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.409: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.409: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.409: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.409: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.409: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.410: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.410: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.410: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.410: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.410: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.410: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.410: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.410: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.411: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.411: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.411: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.411: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.411: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.411: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.411: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.411: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.412: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.412: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.412: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.412: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.412: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.412: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.412: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.412: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.413: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.413: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.413: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.413: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.413: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.413: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.413: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.414: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.414: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.414: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.414: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.414: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.414: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.414: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.415: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.415: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.415: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.415: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.415: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.415: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.415: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.415: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.416: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.416: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.416: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.416: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.416: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.416: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.416: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.416: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.417: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.417: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.417: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.417: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.417: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.417: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.417: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.417: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.418: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.418: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.418: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.418: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.418: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.418: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.418: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.418: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.419: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.419: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.419: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.419: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.419: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.419: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.419: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.419: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.420: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.420: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.421: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.421: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.421: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.421: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.421: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.421: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.421: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.421: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.422: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.422: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.422: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.422: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.422: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.422: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.422: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.422: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.423: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.423: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.423: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.423: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.423: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.423: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.423: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.423: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.424: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.424: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.424: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.424: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.424: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.424: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.424: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.424: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.425: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.425: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.425: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.425: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.425: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.425: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.426: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.426: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.426: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.426: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.426: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.426: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.426: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.426: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.427: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.427: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.427: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.427: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.427: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.427: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.427: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.427: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.428: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.428: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.429: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.429: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.429: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.429: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.429: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.429: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.429: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.429: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.430: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.430: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.430: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.430: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.430: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.430: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.430: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.430: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.431: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.431: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.431: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.431: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.431: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.431: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.431: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.431: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.432: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.432: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.432: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.432: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.432: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.432: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.432: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.432: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.433: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.433: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.433: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.433: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.433: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.433: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.433: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.433: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.434: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.434: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.434: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.434: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.434: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.434: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.435: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.435: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.435: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.435: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.435: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.435: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.435: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.435: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.436: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.436: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.437: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.437: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.437: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.437: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.437: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.437: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.437: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.437: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.438: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.438: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.438: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.438: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.438: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.438: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.438: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.438: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.439: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.439: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.439: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.439: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.439: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.439: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.439: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.439: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.440: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.440: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.440: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.440: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.440: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.440: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.440: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.440: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.441: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.441: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.441: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.441: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.441: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.441: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.441: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.441: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.442: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.442: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.442: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.442: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.442: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.442: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.444: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.444: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.444: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.444: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.444: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.444: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.444: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.444: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.445: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.445: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.445: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.445: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.445: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.445: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.445: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.445: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.446: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.446: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.447: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.447: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.447: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.447: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.447: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.447: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.448: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.448: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.448: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.448: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.448: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.448: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.448: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.448: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.449: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.449: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.450: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.450: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.450: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.450: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.450: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.450: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.450: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.450: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.451: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.451: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.451: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.451: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.451: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.451: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.451: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.451: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.452: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.452: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.452: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.452: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.452: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.452: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.453: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.453: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.453: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.453: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.453: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.453: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.453: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.453: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.454: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.454: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.454: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.454: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.454: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.454: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.454: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.454: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.455: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.455: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.455: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.455: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.455: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.455: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.455: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.455: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.456: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.456: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.456: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.456: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.456: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.456: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.456: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.456: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.457: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.457: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.457: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.458: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.458: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.458: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.458: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.458: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.458: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.458: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.458: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.459: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.459: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.459: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.459: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.459: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.459: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.459: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.460: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.460: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.460: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.460: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.460: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.460: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.460: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.460: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.461: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.461: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.461: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.461: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.461: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.461: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.461: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.461: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.462: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.462: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.462: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.462: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.462: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.462: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.462: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.462: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.463: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.463: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.463: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.463: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.463: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.463: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.463: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.463: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.464: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.464: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.464: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.464: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.464: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.464: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.464: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.464: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.465: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.465: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.465: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.465: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.465: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.465: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.466: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.466: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.466: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.466: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.466: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.466: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.466: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.466: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.467: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.467: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.467: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.467: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.467: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.467: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.467: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.467: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.468: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.468: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.468: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.468: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.468: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.468: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.468: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.468: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.469: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.469: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.469: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.469: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.469: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.469: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.469: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.469: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.470: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.470: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.470: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.470: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.470: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.470: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.470: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.470: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.471: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.471: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.472: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.472: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.472: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.472: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.472: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.472: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.472: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.472: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.473: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.473: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.473: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.473: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.473: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.473: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.473: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.473: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.474: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.474: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.474: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.474: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.474: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.474: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.474: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.474: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.475: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.475: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.475: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.475: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.475: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.475: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.475: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.475: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.476: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.476: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.476: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.476: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.476: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.476: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.477: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.477: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.477: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.477: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.477: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.477: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.477: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.477: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.478: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.478: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.478: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.478: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.478: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.478: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.478: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.478: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.479: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.479: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.479: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.479: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.479: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.479: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.479: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.479: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.480: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.480: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.480: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.480: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.480: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.480: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.480: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.480: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.481: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.481: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.482: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.482: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.482: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.482: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.482: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.482: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.482: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.482: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.483: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.483: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.483: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.483: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.483: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.483: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.483: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.483: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.484: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.484: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.484: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.484: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.484: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.484: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.485: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.485: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.485: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.485: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.485: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.485: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.485: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.485: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.486: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.486: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.486: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.486: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.486: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.486: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.486: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.486: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.487: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.487: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.487: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.487: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.488: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.488: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.488: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.488: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.488: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.488: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.489: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.489: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.489: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.489: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.489: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.489: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.490: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.490: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.490: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.490: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.490: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.490: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.490: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.490: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.491: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.491: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.491: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.491: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.491: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.491: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.491: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.491: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.492: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.492: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.493: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.493: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.493: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.493: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.493: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.493: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.493: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.493: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.494: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.494: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.494: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.494: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.494: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.494: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.494: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.494: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.495: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.495: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.495: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.495: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.495: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.495: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.495: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.495: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.496: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.496: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.496: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.496: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.496: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.496: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.496: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.496: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.497: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.497: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.497: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.497: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.497: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.497: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.497: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.497: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.498: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.498: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.498: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.498: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.498: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.498: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.498: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.498: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.499: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.499: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.499: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.499: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.499: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.499: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.500: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.500: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.501: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.501: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.501: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.501: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.501: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.501: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.502: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.502: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.502: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.502: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.502: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.502: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.502: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.502: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.503: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.503: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.503: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.503: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.503: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.503: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.503: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.503: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.504: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.504: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.508: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.508: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.508: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.508: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.508: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.508: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.509: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.509: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.509: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.509: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.509: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.509: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.509: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.509: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.510: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.510: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.510: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.510: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.510: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.510: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.510: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.510: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.511: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.511: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.512: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.512: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.512: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.512: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.512: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.512: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.512: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.512: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.513: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.513: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.513: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.513: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.513: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.513: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.513: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.513: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.514: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.514: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.514: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.514: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.514: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.514: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.514: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.514: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.515: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.515: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.515: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.515: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.515: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.515: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.515: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.515: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.516: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.516: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.516: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.516: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.516: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.516: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.516: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.516: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.517: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.517: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.517: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.517: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.517: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.517: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.517: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.517: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.518: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.518: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.518: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.518: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.518: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.518: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.519: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.519: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.519: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.519: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.519: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.519: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.519: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.519: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.520: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.520: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.520: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.520: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.520: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.520: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.520: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.520: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.521: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.521: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.521: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.521: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.521: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.521: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.521: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.521: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.522: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.522: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.523: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.523: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.523: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.523: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.523: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.523: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.523: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.523: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.524: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.524: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.524: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.524: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.524: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.524: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.524: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.524: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.525: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.525: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.525: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.525: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.525: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.525: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.525: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.525: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.526: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.526: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.526: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.526: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.526: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.526: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.527: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.527: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.527: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.527: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.527: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.527: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.527: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.527: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.528: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.528: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.528: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.529: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.529: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.529: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.529: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.529: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.529: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.529: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.530: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.530: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.530: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.530: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.530: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.530: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.530: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.530: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.532: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.532: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.532: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.532: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.532: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.532: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.533: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.533: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.534: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.534: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.534: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.534: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.534: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.534: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.534: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.534: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.535: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.535: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.535: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.535: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.535: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.535: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.535: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.535: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.536: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.536: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.536: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.536: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.536: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.536: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.536: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.536: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.537: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.537: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.537: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.537: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.537: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.537: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.537: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.538: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.538: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.538: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.538: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.538: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.538: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.538: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.539: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.539: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.539: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.539: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.539: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.539: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.539: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.539: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.540: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.540: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.541: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.541: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.541: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.541: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.541: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.542: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.542: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.542: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.542: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.542: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.543: [vfs7552] CAPTURE_NUM_STATES entering state 4 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.543: Cleaning image 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.543: variance_after = 20 141s 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.543: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.543: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.543: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.543: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.544: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.544: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.544: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.544: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.544: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.544: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.544: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.545: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.545: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.546: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.546: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.546: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.546: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.546: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.546: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.547: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.547: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.548: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.548: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.548: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.548: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.548: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.548: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.548: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.548: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.549: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.549: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.549: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.549: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.549: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.549: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.550: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.550: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.550: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.550: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.550: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.550: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.550: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.551: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.551: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.551: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.552: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.552: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.552: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.552: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.552: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.552: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.552: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.552: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.553: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.553: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.553: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.553: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.553: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.553: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.553: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.553: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.554: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.554: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.554: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.554: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.554: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.554: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.555: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.555: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.555: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.555: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.555: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.555: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.555: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.555: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.556: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.556: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.556: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.557: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.557: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.557: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.557: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.557: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.557: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.557: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.558: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.558: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.558: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.558: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.558: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.558: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.559: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.559: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.560: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.560: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.560: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.560: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.560: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.560: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.560: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.560: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.561: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.561: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.561: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.561: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.561: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.561: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.561: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.561: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.562: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.562: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.562: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.562: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.562: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.562: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.563: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.563: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.563: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.563: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.563: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.563: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.563: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.563: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.564: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.564: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.564: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.564: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.564: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.564: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.564: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.564: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.565: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.565: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.566: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.566: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.566: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.566: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.566: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.567: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.567: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.567: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.568: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.568: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.568: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.568: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.568: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.568: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.569: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.569: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.569: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.569: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.569: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.569: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.569: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.569: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.570: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.570: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.570: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.570: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.570: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.570: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.570: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.570: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.571: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.571: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.571: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.572: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.572: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.572: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.572: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.572: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.572: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.572: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.573: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.573: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.573: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.573: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.573: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.573: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.573: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.573: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.574: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.574: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.574: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.574: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.574: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.574: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.574: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.574: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.575: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.575: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.575: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.575: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.575: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.575: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.575: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.575: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.576: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.576: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.576: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.576: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.576: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.576: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.576: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.577: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.577: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.577: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.577: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.577: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.577: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.577: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.578: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.578: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.578: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.578: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.578: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.578: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.578: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.578: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.579: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.579: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.579: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.579: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.579: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.579: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.579: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.579: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.580: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.580: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.580: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.580: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.580: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.580: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.580: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.580: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.581: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.581: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.581: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.581: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.581: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.581: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.581: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.581: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.582: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.582: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.582: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.582: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.582: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.582: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.582: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.582: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.583: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.583: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.583: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.584: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.584: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.584: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.584: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.584: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.584: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.584: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.585: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.585: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.585: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.585: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.585: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.585: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.585: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.585: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.587: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.587: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.587: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.587: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.587: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.587: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.587: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.587: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.588: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.588: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.588: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.588: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.588: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.588: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.588: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.589: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.589: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.589: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.589: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.589: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.589: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.589: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.591: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.592: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.592: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.592: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.592: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.592: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.592: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.592: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.593: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.593: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.593: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.593: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.593: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.593: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.593: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.593: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.594: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.594: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.594: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.594: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.595: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.595: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.595: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.595: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.595: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.595: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.596: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.596: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.596: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.596: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.596: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.596: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.600: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.600: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.601: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.601: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.601: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.601: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.601: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.601: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.602: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.602: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.602: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.602: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.602: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.602: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.602: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.602: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.603: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.603: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.603: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.603: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.603: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.603: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.603: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.603: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.604: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.604: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.605: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.605: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.605: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.605: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.605: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.605: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.605: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.605: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.606: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.606: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.606: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.606: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.606: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.606: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.606: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.606: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.607: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.607: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.607: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.607: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.607: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.607: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.608: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.608: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.608: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.608: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.608: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.608: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.608: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.608: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.609: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.609: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.609: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.610: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.610: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.610: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.610: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.610: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.610: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.610: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.611: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.611: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.611: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.611: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.611: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.611: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.611: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.611: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.612: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.612: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.612: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.612: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.612: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.612: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.613: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.613: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.613: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.613: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.613: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.613: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.613: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.613: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.614: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.614: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.614: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.614: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.614: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.614: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.614: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.614: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.615: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.615: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.615: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.615: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.616: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.616: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.616: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.616: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.616: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.616: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.617: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.617: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.617: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.617: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.617: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.617: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.617: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.617: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.618: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.618: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.618: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.618: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.618: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.618: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.618: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.618: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.619: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.619: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.619: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.619: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.619: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.619: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.620: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.620: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.620: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.620: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.620: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.620: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.620: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.620: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.621: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.621: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.621: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.621: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.621: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.621: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.621: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.621: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.622: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.622: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.622: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.622: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.622: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.622: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.622: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.622: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.623: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.623: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.623: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.623: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.623: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.623: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.623: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.623: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.624: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.624: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.624: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.624: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.624: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.624: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.625: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.625: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.625: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.625: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.626: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.626: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.626: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.626: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.626: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.626: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.626: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.626: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.627: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.627: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.627: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.627: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.627: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.627: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.628: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.628: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.628: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.628: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.628: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.628: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.628: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.628: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.629: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.629: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.629: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.629: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.629: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.629: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.629: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.629: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.631: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.631: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.631: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.631: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.631: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.631: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.631: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.631: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.632: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.632: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.632: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.632: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.632: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.632: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.632: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.632: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.633: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.633: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.633: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.633: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.633: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.633: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.633: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.633: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.634: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.634: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.635: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.635: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.635: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.635: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.635: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.635: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.635: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.635: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.636: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.636: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.636: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.636: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.636: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.636: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.637: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.637: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.637: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.637: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.637: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.637: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.637: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.637: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.638: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.638: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.638: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.638: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.638: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.638: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.638: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.638: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.639: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.639: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.639: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.640: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.640: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.640: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.640: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.640: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.640: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.640: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.641: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.641: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.641: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.641: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.641: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.641: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.641: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.641: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.642: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.642: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.642: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.642: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.642: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.642: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.642: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.642: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.643: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.643: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.643: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.644: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.644: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.644: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.644: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.644: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.645: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.645: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.645: [vfs7552] CAPTURE_NUM_STATES entering state 4 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.645: Cleaning image 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.646: variance_after = 17 141s 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.646: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.646: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.646: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.646: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.646: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.647: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.647: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.647: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.647: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.647: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.647: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.648: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.648: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.648: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.648: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.648: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.648: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.648: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.648: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.649: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.649: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.650: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.650: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.650: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.650: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.650: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.650: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.650: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.650: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.651: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.651: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.651: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.651: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.651: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.651: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.652: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.652: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.653: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.653: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.653: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.653: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.653: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.653: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.653: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.653: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.654: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.654: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.654: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.654: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.654: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.654: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.654: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.654: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.655: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.655: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.655: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.655: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.655: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.655: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.656: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.656: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.656: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.656: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.656: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.656: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.657: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.657: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.657: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.657: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.658: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.658: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.658: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.658: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.658: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.658: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.658: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.658: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.659: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.659: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.659: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.659: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.659: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.659: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.660: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.660: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.660: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.660: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.660: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.660: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.660: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.660: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.662: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.662: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.663: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.663: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.663: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.663: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.663: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.663: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.663: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.663: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.664: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.664: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.664: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.664: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.664: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.664: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.665: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.665: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.665: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.665: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.665: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.665: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.665: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.665: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.666: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.666: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.666: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.666: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.666: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.666: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.666: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.666: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.667: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.667: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.667: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.667: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.667: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.667: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.667: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.667: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.668: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.668: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.668: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.668: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.668: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.668: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.668: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.668: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.669: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.669: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.671: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.671: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.671: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.671: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.671: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.671: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.671: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.671: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.672: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.672: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.672: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.672: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.672: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.672: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.673: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.673: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.673: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.673: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.673: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.673: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.673: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.673: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.674: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.674: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.674: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.674: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.674: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.674: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.674: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.674: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.675: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.675: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.676: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.676: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.676: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.676: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.676: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.676: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.677: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.677: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.677: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.677: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.677: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.677: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.678: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.678: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.678: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.678: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.679: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.679: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.679: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.679: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.679: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.679: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.679: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.679: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.680: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.680: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.680: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.680: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.680: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.680: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.681: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.681: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.681: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.681: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.681: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.681: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.681: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.681: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.682: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.682: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.682: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.682: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.682: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.682: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.682: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.682: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.683: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.683: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.684: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.684: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.684: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.684: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.684: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.684: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.684: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.684: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.685: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.685: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.685: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.685: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.685: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.685: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.685: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.685: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.686: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.686: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.686: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.686: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.686: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.686: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.686: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.686: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.687: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.687: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.687: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.687: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.687: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.687: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.688: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.688: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.688: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.688: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.688: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.688: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.688: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.688: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.689: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.689: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.690: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.690: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.690: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.690: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.690: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.690: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.691: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.691: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.691: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.691: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.691: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.691: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.691: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.691: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.692: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.692: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.692: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.692: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.692: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.692: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.692: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.692: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.693: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.693: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.693: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.693: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.693: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.693: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.693: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.693: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.694: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.694: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.695: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.695: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.695: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.695: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.695: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.695: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.695: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.695: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.696: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.696: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.696: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.696: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.696: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.696: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.696: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.696: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.697: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.697: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.697: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.697: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.697: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.697: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.698: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.698: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.699: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.699: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.699: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.699: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.699: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.699: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.699: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.700: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.700: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.700: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.700: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.700: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.700: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.700: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.701: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.701: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.701: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.701: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.701: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.701: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.701: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.701: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.702: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.702: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.702: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.703: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.703: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.703: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.703: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.703: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.703: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.703: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.704: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.704: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.704: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.704: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.704: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.704: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.704: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.704: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.705: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.705: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.705: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.705: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.705: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.705: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.706: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.706: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.706: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.706: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.706: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.706: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.706: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.706: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.707: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.707: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.707: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.707: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.707: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.707: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.707: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.707: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.708: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.708: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.709: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.709: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.709: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.709: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.709: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.709: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.709: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.709: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.710: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.710: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.710: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.710: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.710: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.710: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.710: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.710: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.711: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.712: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.712: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.712: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.712: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.713: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.713: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.713: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.713: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.713: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.714: [vfs7552] CAPTURE_NUM_STATES entering state 4 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.714: Cleaning image 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.714: variance_after = 17 141s 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.714: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.714: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.714: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.714: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.715: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.715: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.715: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.715: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.715: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.715: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.715: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.716: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.716: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.716: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.716: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.716: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.716: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.716: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.716: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.717: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.717: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.718: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.718: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.718: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.718: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.718: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.718: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.718: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.718: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.719: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.719: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.719: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.719: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.719: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.719: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.719: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.719: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.720: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.720: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.720: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.720: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.720: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.720: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.720: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.720: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.721: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.721: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.721: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.721: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.721: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.721: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.721: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.722: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.722: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.722: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.722: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.722: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.722: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.722: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.723: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.723: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.723: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.723: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.723: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.723: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.723: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.723: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.724: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.724: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.725: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.725: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.725: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.725: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.725: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.725: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.729: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.729: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.729: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.730: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.730: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.730: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.730: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.730: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.730: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.730: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.731: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.731: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.731: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.731: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.731: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.731: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.731: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.731: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.732: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.732: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.732: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.732: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.732: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.732: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.732: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.732: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.733: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.733: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.733: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.733: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.733: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.733: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.734: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.734: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.735: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.735: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.735: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.735: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.735: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.735: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.735: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.735: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.736: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.736: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.736: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.736: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.736: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.736: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.736: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.736: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.737: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.737: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.737: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.737: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.737: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.737: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.737: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.737: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.738: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.738: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.738: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.738: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.738: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.738: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.738: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.738: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.739: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.739: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.739: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.739: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.739: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.739: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.740: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.740: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.740: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.740: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.740: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.740: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.740: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.740: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.741: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.741: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.741: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.741: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.741: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.741: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.741: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.741: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.742: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.742: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.742: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.742: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.742: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.742: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.742: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.742: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.743: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.743: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.743: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.743: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.743: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.743: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.743: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.743: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.744: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.744: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.744: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.744: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.744: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.744: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.744: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.744: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.745: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.745: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.745: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.745: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.745: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.745: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.745: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.745: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.746: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.746: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.746: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.746: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.746: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.746: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.746: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.746: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.747: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.747: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.747: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.747: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.747: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.747: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.747: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.747: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.748: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.748: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.749: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.749: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.749: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.749: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.749: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.749: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.749: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.749: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.750: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.750: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.750: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.750: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.750: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.750: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.750: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.750: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.751: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.751: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.751: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.751: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.751: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.751: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.751: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.751: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.752: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.752: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.752: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.752: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.752: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.752: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.753: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.753: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.753: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.753: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.753: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.753: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.753: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.753: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.754: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.754: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.754: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.754: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.754: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.754: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.754: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.754: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.755: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.755: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.755: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.755: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.755: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.755: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.755: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.755: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.756: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.756: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.756: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.757: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.757: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.757: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.757: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.757: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.757: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.757: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.758: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.758: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.758: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.758: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.758: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.758: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.758: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.758: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.759: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.759: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.759: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.759: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.759: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.759: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.759: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.759: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.760: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.760: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.760: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.760: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.760: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.760: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.760: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.760: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.761: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.761: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.761: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.761: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.761: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.761: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.761: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.761: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.762: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.762: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.762: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.762: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.762: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.762: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.762: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.762: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.763: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.763: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.763: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.763: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.763: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.763: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.764: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.764: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.765: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.765: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.765: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.765: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.765: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.765: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.765: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.765: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.766: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.766: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.766: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.766: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.766: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.766: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.766: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.766: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.767: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.767: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.767: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.767: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.767: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.767: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.767: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.768: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.768: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.768: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.768: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.768: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.768: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.768: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.769: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.769: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.769: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.769: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.769: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.769: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.769: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.769: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.770: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.770: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.770: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.770: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.770: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.770: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.770: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.770: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.771: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.771: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.771: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.771: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.771: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.772: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.772: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.772: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.772: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.772: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.773: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.773: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.773: [vfs7552] CAPTURE_NUM_STATES entering state 4 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.773: Cleaning image 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.774: variance_after = 17 141s 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.774: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.774: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.774: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.774: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.774: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.775: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.775: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.775: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.775: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.775: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.775: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.775: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.775: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.776: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.776: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.776: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.776: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.776: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.776: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.776: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.776: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.777: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.777: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.777: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.777: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.777: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.777: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.777: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.777: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.778: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.778: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.778: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.778: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.778: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.778: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.778: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.778: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.779: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.779: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.779: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.779: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.779: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.779: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.779: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.779: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.780: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.780: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.780: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.780: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.780: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.780: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.780: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.780: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.781: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.781: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.781: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.781: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.781: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.781: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.781: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.781: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.782: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.782: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.782: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.782: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.782: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.782: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.782: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.782: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.783: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.783: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.783: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.783: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.783: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.783: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.783: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.783: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.784: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.784: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.784: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.784: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.784: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.784: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.784: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.784: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.785: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.785: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.785: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.785: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.785: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.785: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.785: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.786: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.786: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.786: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.786: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.786: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.786: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.786: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.787: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.787: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.788: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.788: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.788: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.788: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.788: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.788: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.788: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.788: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.789: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.789: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.789: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.789: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.789: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.789: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.789: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.789: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.790: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.790: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.790: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.790: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.790: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.790: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.790: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.791: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.791: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.791: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.791: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.791: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.791: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.791: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.792: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.792: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.792: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.792: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.792: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.792: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.792: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.792: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.793: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.793: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.793: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.793: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.793: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.793: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.793: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.793: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.794: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.794: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.794: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.794: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.794: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.794: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.794: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.794: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.795: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.795: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.795: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.795: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.795: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.795: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.795: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.795: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.796: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.796: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.797: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.797: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.797: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.797: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.797: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.797: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.797: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.797: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.798: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.798: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.798: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.798: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.798: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.798: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.798: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.798: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.799: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.799: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.799: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.799: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.799: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.799: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.799: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.799: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.800: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.800: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.800: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.800: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.800: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.800: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.800: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.800: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.801: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.801: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.801: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.801: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.801: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.801: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.801: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.801: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.802: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.802: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.802: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.802: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.802: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.802: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.803: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.803: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.803: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.803: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.803: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.803: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.803: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.803: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.804: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.804: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.805: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.805: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.805: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.805: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.805: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.805: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.805: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.805: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.806: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.806: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.806: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.806: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.806: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.806: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.806: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.807: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.807: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.807: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.807: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.807: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.807: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.807: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.808: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.808: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.808: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.808: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.809: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.809: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.809: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.809: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.809: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.809: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.810: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.810: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.810: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.810: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.810: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.810: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.810: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.810: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.811: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.811: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.811: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.811: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.811: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.811: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.811: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.811: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.812: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.812: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.812: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.812: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.812: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.812: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.812: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.812: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.813: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.813: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.813: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.813: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.813: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.813: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.813: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.813: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.814: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.814: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.814: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.814: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.814: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.814: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.814: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.814: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.815: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.815: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.815: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.815: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.815: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.815: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.815: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.816: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.816: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.816: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.816: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.816: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.816: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.816: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.817: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.817: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.817: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.817: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.817: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.817: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.817: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.817: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.818: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.818: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.818: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.818: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.818: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.818: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.818: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.818: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.819: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.819: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.819: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.819: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.819: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.819: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.819: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.819: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.820: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.820: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.820: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.820: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.820: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.821: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.821: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.821: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.821: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.822: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.822: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.822: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.822: [vfs7552] CAPTURE_NUM_STATES entering state 4 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.823: Cleaning image 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.823: variance_after = 17 141s 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.823: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.823: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.823: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.823: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.823: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.824: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.824: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.824: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.824: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.824: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.824: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.824: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.824: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.825: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.825: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.825: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.825: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.825: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.825: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.825: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.825: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.826: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.826: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.826: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.826: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.826: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.826: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.826: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.826: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.827: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.827: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.827: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.827: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.827: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.827: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.827: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.827: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.828: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.828: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.828: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.828: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.828: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.828: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.828: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.828: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.829: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.829: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.829: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.829: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.829: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.829: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.829: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.829: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.830: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.830: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.830: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.830: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.830: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.830: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.830: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.830: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.831: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.831: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.831: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.831: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.831: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.831: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.831: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.831: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.832: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.832: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.832: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.832: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.832: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.832: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.833: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.833: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.833: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.833: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.833: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.833: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.833: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.833: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.834: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.834: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.834: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.834: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.834: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.834: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.834: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.834: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.835: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.835: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.835: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.835: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.835: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.835: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.835: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.835: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.836: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.836: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.836: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.836: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.836: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.836: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.836: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.836: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.837: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.837: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.838: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.838: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.838: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.838: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.838: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.838: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.839: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.839: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.839: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.839: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.839: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.839: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.839: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.839: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.840: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.840: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.840: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.841: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.841: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.841: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.841: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.841: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.841: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.841: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.841: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.841: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.841: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.841: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.841: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.842: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.842: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.842: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.843: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.843: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.843: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.843: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.843: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.843: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.843: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.843: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.844: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.844: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.844: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.845: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.845: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.845: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.845: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.845: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.846: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.846: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.846: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.846: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.846: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.846: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.846: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.846: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.847: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.847: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.847: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.847: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.847: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.847: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.847: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.847: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.848: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.848: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.848: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.848: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.848: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.848: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.848: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.848: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.849: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.849: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.849: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.849: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.849: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.849: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.849: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.849: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.850: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.850: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.850: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.850: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.850: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.850: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.850: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.850: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.851: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.851: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.851: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.851: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.851: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.851: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.851: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.851: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.852: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.852: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.852: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.852: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.852: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.852: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.852: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.853: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.853: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.853: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.853: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.853: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.853: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.853: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.854: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.854: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.854: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.854: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.854: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.854: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.854: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.854: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.855: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.855: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.855: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.855: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.855: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.855: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.855: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.855: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.856: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.856: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.856: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.856: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.856: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.856: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.856: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.856: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.857: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.857: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.857: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.857: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.857: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.857: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.857: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.857: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.858: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.858: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.858: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.858: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.858: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.858: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.858: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.858: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.859: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.859: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.860: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.860: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.860: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.860: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.860: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.860: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.860: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.860: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.861: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.861: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.861: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.861: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.861: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.861: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.861: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.861: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.862: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.862: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.862: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.862: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.862: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.862: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.865: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.865: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.866: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.866: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.866: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.866: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.866: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.866: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.866: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.866: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.867: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.867: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.867: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.867: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.867: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.867: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.867: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.867: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.868: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.868: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.868: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.868: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.868: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.868: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.868: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.868: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.869: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.869: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.869: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.869: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.869: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.869: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.869: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.869: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.870: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.870: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.870: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.870: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.870: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.870: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.870: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.870: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.871: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.871: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.871: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.871: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.871: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.871: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.871: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.871: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.872: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.872: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.872: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.872: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.872: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.872: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.872: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.872: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.873: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.873: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.873: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.873: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.873: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.873: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.873: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.874: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.874: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.874: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.874: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.874: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.874: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.874: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.874: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.875: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.875: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.875: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.875: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.875: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.875: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.875: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.875: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.876: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.876: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.876: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.876: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.877: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.877: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.877: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.877: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.877: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.878: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.878: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.878: [vfs7552] CAPTURE_NUM_STATES entering state 4 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.878: Cleaning image 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.878: variance_after = 16 141s 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.878: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.878: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.878: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.879: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.879: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.879: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.879: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.879: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.879: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.879: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.879: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.880: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.880: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.881: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.881: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.881: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.881: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.881: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.881: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.881: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.881: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.882: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.882: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.882: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.882: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.882: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.882: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.882: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.882: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.883: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.883: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.883: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.883: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.883: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.883: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.883: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.883: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.884: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.884: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.884: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.884: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.884: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.884: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.884: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.884: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.885: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.885: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.885: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.885: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.885: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.885: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.885: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.885: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.888: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.888: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.888: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.888: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.888: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.888: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.889: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.889: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.890: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.890: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.890: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.890: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.890: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.890: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.890: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.890: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.891: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.891: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.891: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.891: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.891: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.891: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.891: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.891: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.892: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.892: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.892: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.892: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.892: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.892: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.892: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.892: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.893: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.893: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.893: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.893: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.893: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.893: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.893: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.893: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.894: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.894: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.894: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.894: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.894: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.894: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.894: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.894: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.895: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.895: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.895: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.895: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.895: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.895: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.895: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.895: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.896: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.896: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.896: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.896: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.896: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.896: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.896: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.896: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.897: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.897: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.897: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.897: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.897: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.897: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.898: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.898: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.898: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.898: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.898: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.898: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.898: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.898: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.899: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.899: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.899: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.899: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.899: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.899: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.899: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.899: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.900: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.900: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.900: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.900: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.900: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.900: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.900: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.900: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.901: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.901: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.902: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.902: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.902: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.902: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.902: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.902: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.902: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.902: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.903: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.903: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.903: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.903: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.903: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.903: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.903: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.903: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.904: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.904: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.904: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.904: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.904: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.904: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.904: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.904: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.905: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.905: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.905: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.905: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.905: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.905: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.905: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.905: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.906: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.906: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.906: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.906: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.906: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.906: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.906: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.906: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.907: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.907: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.907: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.907: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.907: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.907: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.907: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.907: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.908: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.908: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.908: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.908: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.908: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.908: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.909: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.909: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.909: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.909: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.909: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.909: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.909: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.909: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.910: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.910: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.910: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.910: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.910: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.910: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.910: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.910: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.911: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.911: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.911: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.911: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.911: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.911: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.911: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.911: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.912: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.912: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.913: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.913: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.913: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.913: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.913: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.913: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.913: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.913: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.914: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.914: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.914: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.914: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.914: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.914: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.914: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.914: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.915: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.915: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.915: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.915: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.915: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.915: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.915: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.915: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.916: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.916: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.916: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.916: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.916: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.916: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.916: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.916: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.917: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.917: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.917: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.917: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.917: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.917: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.917: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.917: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.918: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.918: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.918: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.918: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.918: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.918: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.918: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.918: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.919: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.919: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.919: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.919: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.919: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.919: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.919: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.919: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.920: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.920: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.920: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.920: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.920: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.920: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.920: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.920: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.921: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.921: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.921: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.921: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.921: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.921: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.921: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.921: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.922: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.922: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.922: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.922: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.922: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.922: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.922: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.923: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.923: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.923: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.923: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.923: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.923: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.923: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.924: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.924: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.924: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.924: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.924: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.924: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.924: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.924: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.925: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.925: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.925: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.925: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.925: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.925: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.925: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.925: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.926: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.926: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.926: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.926: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.926: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.926: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.926: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.926: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.927: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.927: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.927: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.927: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.927: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.927: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.927: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.927: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.928: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.928: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.928: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.928: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.928: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.928: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.928: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.928: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.929: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.929: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.929: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.929: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.929: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.930: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.930: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.930: [vfs7552] CAPTURE_NUM_STATES entering state 2 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.930: [vfs7552] REQUEST CHUNK entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.930: Sending vfs7552_read_image_chunk 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.931: [vfs7552] REQUEST CHUNK completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.931: [vfs7552] CAPTURE_NUM_STATES entering state 3 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.931: [vfs7552] CAPTURE_NUM_STATES entering state 4 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.931: Cleaning image 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.931: variance_after = 17 141s 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.931: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.931: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.931: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.932: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.932: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.933: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.933: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.933: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.933: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.933: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.933: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.933: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.933: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.934: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.934: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.934: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.934: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.934: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.934: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.934: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.934: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.935: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.935: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.935: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.935: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.935: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.935: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.935: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.935: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.936: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.936: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.936: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.936: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.936: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.936: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.936: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.936: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.937: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.937: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.937: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.937: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.937: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.937: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.937: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.937: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.938: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.938: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.938: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.938: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.938: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.938: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.938: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.938: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.939: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.939: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.939: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.939: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.939: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.939: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.939: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.939: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.940: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.940: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.940: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.940: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.940: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.940: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.940: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.940: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.941: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.941: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.941: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.941: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.941: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.941: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.941: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.941: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.942: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.942: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.942: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.942: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.942: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.942: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.942: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.943: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.943: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.943: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.943: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.943: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.943: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.943: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.944: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.944: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.944: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.944: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.944: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.944: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.944: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.944: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.945: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.945: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.945: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.945: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.945: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.945: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.945: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.945: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.946: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.946: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.946: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.946: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.946: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.946: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.946: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.946: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.947: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.947: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.947: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.947: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.947: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.947: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.947: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.947: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.948: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.948: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.948: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.948: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.948: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.948: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.948: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.948: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.949: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.949: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.950: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.950: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.950: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.950: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.950: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.950: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.950: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.950: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.951: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.951: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.951: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.951: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.951: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.951: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.951: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.951: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.952: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.952: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.952: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.952: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.952: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.952: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.952: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.952: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.953: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.953: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.953: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.953: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.953: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.953: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.953: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.953: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.954: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.954: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.954: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.954: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.954: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.954: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.954: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.954: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.955: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.955: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.955: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.955: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.955: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.955: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.955: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.955: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.956: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.956: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.956: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.956: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.956: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.956: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.956: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.956: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.957: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.957: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.957: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.957: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.957: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.957: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.957: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.958: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.958: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.958: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.958: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.958: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.958: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.958: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.958: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.958: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.959: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.959: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.959: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.959: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.959: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.959: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.959: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.960: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.960: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.960: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.960: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.960: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.960: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.960: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.961: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.961: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.961: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.961: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.961: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.961: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.961: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.961: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.962: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.962: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.962: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.962: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.962: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.962: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.962: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.962: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.963: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.963: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.963: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.963: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.963: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.963: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.963: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.963: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.964: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.964: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.964: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.964: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.964: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.964: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.964: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.964: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.965: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.965: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.965: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.965: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.965: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.965: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.965: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.965: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.966: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.966: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.966: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.966: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.966: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.966: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.966: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.966: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.967: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.967: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.967: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.967: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.967: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.967: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.967: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.967: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.968: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.968: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.969: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.969: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.969: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.969: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.969: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.969: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.969: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.969: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.970: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.970: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.970: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.970: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.970: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.970: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.970: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.970: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.971: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.971: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.971: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.971: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.971: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.971: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.971: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.971: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.972: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.972: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.972: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.972: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.972: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.972: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.972: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.972: Receiving 64 bytes 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.973: Got 6 bytes out of 64 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.973: [vfs7552] QUERY DATA READY completed successfully 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.973: [vfs7552] CAPTURE_NUM_STATES entering state 1 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.973: [vfs7552] CAPTURE_NUM_STATES entering state 0 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.973: [vfs7552] QUERY DATA READY entering state 0 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.973: Sending vfs7552_is_image_ready 141s (process:4102): libfprint-SSM-DEBUG: 03:38:08.973: [vfs7552] QUERY DATA READY entering state 1 141s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.973: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.974: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.974: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.974: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.974: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.974: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.974: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.974: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.974: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.975: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.975: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.975: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.975: [vfs7552] CAPTURE_NUM_STATES entering state 2 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.975: [vfs7552] REQUEST CHUNK entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.975: Sending vfs7552_read_image_chunk 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.975: [vfs7552] REQUEST CHUNK completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.976: [vfs7552] CAPTURE_NUM_STATES entering state 3 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.976: [vfs7552] CAPTURE_NUM_STATES entering state 2 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.976: [vfs7552] REQUEST CHUNK entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.976: Sending vfs7552_read_image_chunk 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.977: [vfs7552] REQUEST CHUNK completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.977: [vfs7552] CAPTURE_NUM_STATES entering state 3 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.977: [vfs7552] CAPTURE_NUM_STATES entering state 2 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.977: [vfs7552] REQUEST CHUNK entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.977: Sending vfs7552_read_image_chunk 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.978: [vfs7552] REQUEST CHUNK completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.978: [vfs7552] CAPTURE_NUM_STATES entering state 3 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.978: [vfs7552] CAPTURE_NUM_STATES entering state 4 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.978: Cleaning image 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.978: variance_after = 16 142s 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.978: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.978: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.978: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.979: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.979: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.979: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.979: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.979: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.979: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.979: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.979: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.980: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.980: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.980: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.981: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.981: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.981: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.981: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.981: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.981: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.981: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.981: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.982: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.982: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.982: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.982: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.982: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.982: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.982: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.983: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.983: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.983: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.983: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.983: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.983: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.983: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.983: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.984: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.984: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.984: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.984: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.984: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.984: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.984: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.984: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.985: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.985: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.985: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.985: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.985: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.985: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.987: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.987: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.987: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.987: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.987: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.987: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.987: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.987: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.988: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.988: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.988: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.988: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.988: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.988: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.988: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.988: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.989: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.989: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.989: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.989: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.989: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.989: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.989: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.989: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.990: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.990: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.990: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.990: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.990: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.990: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.990: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.990: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.991: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.991: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.991: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.991: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.991: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.991: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.991: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.991: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.992: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.992: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.996: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.996: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.996: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.996: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.996: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.996: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.997: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.997: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.997: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.997: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.997: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.997: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.997: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.998: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.998: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.998: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.998: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.998: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.998: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.998: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.998: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.998: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:08.999: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:08.999: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.000: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.000: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.000: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.000: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.000: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.000: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.000: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.000: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.001: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.001: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.001: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.001: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.001: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.001: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.001: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.001: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.002: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.002: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.002: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.002: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.002: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.002: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.002: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.002: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.003: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.003: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.003: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.003: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.003: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.003: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.003: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.003: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.004: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.004: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.004: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.004: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.004: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.004: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.004: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.004: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.005: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.005: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.005: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.005: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.005: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.005: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.005: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.005: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.006: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.006: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.006: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.006: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.006: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.006: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.006: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.006: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.007: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.007: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.007: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.007: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.007: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.007: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.007: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.007: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.008: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.008: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.008: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.008: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.008: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.008: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.008: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.008: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.009: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.009: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.009: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.009: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.009: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.009: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.010: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.010: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.010: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.010: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.010: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.010: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.010: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.010: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.011: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.011: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.011: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.011: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.011: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.011: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.011: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.011: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.012: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.012: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.012: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.012: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.012: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.012: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.012: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.012: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.013: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.013: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.013: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.013: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.013: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.013: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.013: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.013: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.014: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.014: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.014: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.014: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.014: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.014: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.015: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.015: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.015: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.015: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.016: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.016: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.016: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.016: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.016: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.016: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.016: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.016: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.017: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.017: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.017: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.017: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.017: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.017: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.017: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.017: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.018: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.018: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.018: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.018: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.018: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.018: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.018: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.019: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.019: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.019: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.019: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.019: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.019: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.019: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.020: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.020: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.020: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.020: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.020: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.020: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.020: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.020: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.021: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.021: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.021: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.021: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.021: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.021: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.021: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.021: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.022: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.022: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.022: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.022: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.022: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.022: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.022: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.022: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.023: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.023: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.023: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.023: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.023: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.023: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.023: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.023: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.024: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.024: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.025: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.025: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.025: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.025: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.025: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.025: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.025: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.025: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.026: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.026: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.026: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.026: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.026: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.026: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.026: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.026: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.027: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.027: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.027: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.027: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.027: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.027: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.027: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.027: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.028: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.028: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.028: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.028: [vfs7552] CAPTURE_NUM_STATES entering state 2 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.028: [vfs7552] REQUEST CHUNK entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.028: Sending vfs7552_read_image_chunk 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.028: [vfs7552] REQUEST CHUNK completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.028: [vfs7552] CAPTURE_NUM_STATES entering state 3 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.029: [vfs7552] CAPTURE_NUM_STATES entering state 2 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.029: [vfs7552] REQUEST CHUNK entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.029: Sending vfs7552_read_image_chunk 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.029: [vfs7552] REQUEST CHUNK completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.029: [vfs7552] CAPTURE_NUM_STATES entering state 3 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.030: [vfs7552] CAPTURE_NUM_STATES entering state 2 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.030: [vfs7552] REQUEST CHUNK entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.030: Sending vfs7552_read_image_chunk 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.031: [vfs7552] REQUEST CHUNK completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.031: [vfs7552] CAPTURE_NUM_STATES entering state 3 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.031: [vfs7552] CAPTURE_NUM_STATES entering state 4 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.031: Cleaning image 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.031: variance_after = 2168 142s 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.031: [vfs7552] CAPTURE_NUM_STATES completed successfully 142s (process:4102): libfprint-device-DEBUG: 03:38:09.031: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 142s (process:4102): libfprint-image_device-DEBUG: 03:38:09.031: Image device reported finger status: on 142s (process:4102): libfprint-image_device-DEBUG: 03:38:09.031: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.081: changing to 2 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.081: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.081: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.081: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.082: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.083: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.083: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.083: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.083: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.083: [vfs7552] CAPTURE_NUM_STATES entering state 2 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.083: [vfs7552] REQUEST CHUNK entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.083: Sending vfs7552_read_image_chunk 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.084: [vfs7552] REQUEST CHUNK completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.084: [vfs7552] CAPTURE_NUM_STATES entering state 3 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.085: [vfs7552] CAPTURE_NUM_STATES entering state 2 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.085: [vfs7552] REQUEST CHUNK entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.085: Sending vfs7552_read_image_chunk 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.085: [vfs7552] REQUEST CHUNK completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.085: [vfs7552] CAPTURE_NUM_STATES entering state 3 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.086: [vfs7552] CAPTURE_NUM_STATES entering state 2 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.086: [vfs7552] REQUEST CHUNK entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.086: Sending vfs7552_read_image_chunk 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.087: [vfs7552] REQUEST CHUNK completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.087: [vfs7552] CAPTURE_NUM_STATES entering state 3 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.087: [vfs7552] CAPTURE_NUM_STATES entering state 4 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.087: Cleaning image 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.087: variance_after = 2082 142s 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.087: [vfs7552] CAPTURE_NUM_STATES completed successfully 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.087: Image captured 142s (process:4102): libfprint-image_device-DEBUG: 03:38:09.087: Image device captured an image 142s (process:4102): libfprint-image_device-DEBUG: 03:38:09.088: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 142s (process:4102): libfprint-device-DEBUG: 03:38:09.092: Device reported finger status change: FP_FINGER_STATUS_PRESENT 142s (process:4102): libfprint-image-DEBUG: 03:38:09.121: Minutiae scan completed in 0.033260 secs 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.137: changing to 3 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.137: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.137: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.137: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.138: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.138: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.138: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.139: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.139: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.139: [vfs7552] CAPTURE_NUM_STATES entering state 2 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.139: [vfs7552] REQUEST CHUNK entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.139: Sending vfs7552_read_image_chunk 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.139: [vfs7552] REQUEST CHUNK completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.139: [vfs7552] CAPTURE_NUM_STATES entering state 3 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.140: [vfs7552] CAPTURE_NUM_STATES entering state 2 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.140: [vfs7552] REQUEST CHUNK entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.140: Sending vfs7552_read_image_chunk 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.140: [vfs7552] REQUEST CHUNK completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.140: [vfs7552] CAPTURE_NUM_STATES entering state 3 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.141: [vfs7552] CAPTURE_NUM_STATES entering state 2 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.141: [vfs7552] REQUEST CHUNK entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.141: Sending vfs7552_read_image_chunk 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.141: [vfs7552] REQUEST CHUNK completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.141: [vfs7552] CAPTURE_NUM_STATES entering state 3 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.142: [vfs7552] CAPTURE_NUM_STATES entering state 4 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.142: Cleaning image 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.142: variance_after = 2003 142s 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.142: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.142: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.142: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.143: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.143: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.143: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.143: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.143: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.143: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.143: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.144: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.144: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.144: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.145: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.145: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.145: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.145: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.145: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.145: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.145: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.145: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.146: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.146: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.146: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.146: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.146: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.146: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.146: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.146: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.147: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.147: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.147: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.147: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.147: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.147: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.147: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.147: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.148: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.148: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.148: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.148: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.148: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.148: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.149: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.149: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.149: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.149: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.149: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.149: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.149: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.149: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.150: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.150: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.150: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.150: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.150: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.150: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.150: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.150: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.151: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.151: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.152: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.152: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.152: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.152: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.152: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.152: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.152: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.152: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.153: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.153: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.153: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.153: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.153: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.153: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.153: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.153: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.154: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.154: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.154: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.154: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.154: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.154: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.155: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.155: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.155: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.155: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.155: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.155: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.155: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.155: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.156: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.156: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.156: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.156: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.157: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.157: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.157: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.157: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.157: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.157: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.158: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.158: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.158: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.158: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.158: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.158: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.158: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.158: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.159: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.159: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.159: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.159: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.159: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.159: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.159: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.159: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.160: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.160: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.160: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.160: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.160: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.160: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.161: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.161: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.161: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.161: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.161: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.161: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.161: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.161: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.162: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.162: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.162: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.162: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.162: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.162: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.162: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.162: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.163: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.163: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.163: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.163: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.163: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.163: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.163: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.163: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.164: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.164: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.165: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.165: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.165: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.165: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.165: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.165: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.165: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.165: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.165: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.166: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.166: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.166: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.166: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.166: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.166: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.166: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.167: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.167: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.167: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.167: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.167: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.167: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.167: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.167: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.168: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.168: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.168: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.168: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.168: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.168: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.168: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.168: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.169: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.169: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.169: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.169: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.169: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.169: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.169: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.169: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.170: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.170: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.170: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.170: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.170: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.170: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.171: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.171: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.171: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.171: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.171: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.171: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.171: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.171: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.172: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.172: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.173: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.173: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.173: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.173: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.173: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.173: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.173: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.173: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.174: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.174: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.174: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.174: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.174: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.174: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.174: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.174: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.175: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.175: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.175: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.175: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.175: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.175: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.176: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.176: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.176: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.176: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.176: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.176: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.176: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.176: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.177: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.177: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.177: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.177: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.177: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.177: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.177: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.177: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.178: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.178: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.178: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.178: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.178: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.178: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.178: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.178: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.179: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.179: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.179: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.179: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.179: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.179: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.179: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.179: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.180: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.180: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.180: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.180: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.180: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.180: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.180: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.180: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.181: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.181: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.182: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.182: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.182: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.182: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.182: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.182: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.182: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.182: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.183: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.183: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.183: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.183: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.183: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.183: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.183: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.183: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.184: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.184: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.184: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.184: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.184: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.184: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.185: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.185: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.185: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.185: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.185: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.185: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.185: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.185: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.186: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.186: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.186: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.186: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.186: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.186: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.186: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.186: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.187: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.187: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.187: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.187: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.187: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.187: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.187: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.187: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.188: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.188: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.189: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.189: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.189: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.189: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.189: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.189: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.189: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.189: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.190: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.190: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.190: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.190: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.190: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.190: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.190: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.190: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.191: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.191: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.191: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.191: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.191: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.191: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.191: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.191: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.192: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.192: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.192: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.192: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.192: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.192: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.193: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.193: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.193: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.193: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.193: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.193: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.193: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.193: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.194: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.194: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.194: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.194: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.194: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.194: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.194: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.194: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.195: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.195: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.196: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.196: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.196: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.196: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.196: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.196: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.196: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.196: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.197: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.197: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.197: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.197: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.197: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.197: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.197: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.197: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.198: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.198: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.198: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.198: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.198: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.198: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.199: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.199: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.199: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.199: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.199: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.199: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.199: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.199: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.200: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.200: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.200: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.200: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.200: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.200: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.200: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.200: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.201: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.201: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.202: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.202: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.202: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.202: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.202: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.202: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.202: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.202: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.203: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.203: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.203: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.203: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.203: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.203: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.204: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.204: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.204: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.204: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.204: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.204: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.204: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.204: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.205: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.205: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.205: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.205: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.205: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.205: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.205: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.205: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.206: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.206: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.207: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.207: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.207: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.207: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.207: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.207: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.207: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.207: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.208: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.208: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.208: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.208: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.208: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.208: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.209: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.209: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.209: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.209: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.209: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.209: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.209: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.209: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.210: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.210: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.210: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.210: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.210: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.210: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.210: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.210: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.211: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.211: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.212: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.212: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.212: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.212: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.212: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.212: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.212: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.212: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.213: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.213: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.213: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.213: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.213: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.213: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.213: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.213: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.214: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.214: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.214: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.214: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.214: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.214: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.215: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.215: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.215: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.215: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.215: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.215: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.215: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.215: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.216: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.216: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.216: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.216: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.216: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.216: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.216: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.216: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.217: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.217: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.217: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.217: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.217: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.217: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.217: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.217: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.218: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.218: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.219: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.219: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.219: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.219: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.219: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.219: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.219: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.219: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.220: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.220: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.220: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.220: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.220: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.220: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.220: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.220: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.221: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.221: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.221: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.221: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.221: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.221: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.221: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.221: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.222: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.222: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.222: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.222: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.222: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.222: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.222: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.222: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.223: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.223: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.223: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.223: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.223: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.223: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.224: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.224: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.224: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.224: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.224: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.224: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.224: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.224: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.225: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.225: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.225: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.225: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.225: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.225: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.225: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.225: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.226: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.226: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.226: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.226: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.226: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.226: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.226: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.226: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.227: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.227: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.227: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.228: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.228: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.228: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.228: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.228: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.228: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.228: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.229: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.229: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.229: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.229: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.229: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.229: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.229: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.229: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.230: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.230: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.230: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.230: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.230: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.230: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.230: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.230: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.231: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.231: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.231: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.231: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.231: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.231: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.231: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.231: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.232: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.232: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.232: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.232: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.232: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.232: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.233: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.233: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.233: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.233: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.233: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.233: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.233: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.233: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.234: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.234: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.234: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.234: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.234: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.234: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.234: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.234: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.235: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.235: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.236: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.236: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.236: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.236: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.236: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.236: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.236: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.236: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.237: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.237: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.237: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.237: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.237: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.237: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.237: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.237: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.238: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.238: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.238: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.238: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.238: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.238: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.238: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.238: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.239: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.239: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.239: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.239: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.239: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.239: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.240: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.240: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.240: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.240: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.240: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.240: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.240: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.240: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.241: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.241: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.241: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.241: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.241: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.241: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.241: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.241: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.242: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.242: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.242: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.242: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.242: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.242: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.242: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.243: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.243: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.243: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.244: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.244: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.244: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.244: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.244: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.244: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.244: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.244: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.245: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.245: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.245: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.245: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.245: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.245: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.245: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.245: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.246: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.246: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.246: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.246: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.246: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.246: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.246: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.246: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.247: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.247: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.247: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.247: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.247: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.247: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.248: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.248: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.248: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.248: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.248: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.248: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.248: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.248: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.249: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.249: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.249: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.249: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.249: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.249: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.249: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.249: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.250: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.250: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.250: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.250: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.250: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.250: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.250: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.250: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.251: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.251: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.252: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.252: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.252: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.252: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.252: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.252: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.252: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.252: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.253: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.253: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.253: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.253: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.253: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.253: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.253: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.253: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.254: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.254: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.254: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.254: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.254: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.254: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.254: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.255: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.255: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.255: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.255: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.255: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.255: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.255: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.256: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.256: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.256: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.256: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.256: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.256: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.256: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.256: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.257: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.257: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.257: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.257: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.257: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.257: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.257: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.257: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.258: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.258: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.259: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.259: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.259: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.259: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.259: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.259: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.259: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.259: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.260: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.260: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.260: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.260: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.260: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.260: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.260: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.260: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.261: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.261: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.261: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.261: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.261: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.261: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.261: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.261: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.262: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.262: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.262: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.262: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.262: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.262: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.263: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.263: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.263: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.263: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.263: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.263: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.263: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.263: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.264: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.264: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.265: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.265: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.265: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.265: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.265: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.265: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.265: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.265: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.266: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.266: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.266: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.266: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.266: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.266: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.266: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.266: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.267: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.267: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.267: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.267: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.267: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.267: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.268: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.268: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.268: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.268: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.268: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.268: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.268: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.268: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.269: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.269: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.269: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.269: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.269: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.269: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.269: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.269: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.270: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.270: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.271: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.271: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.271: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.271: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.271: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.271: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.271: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.271: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.272: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.272: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.272: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.272: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.272: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.272: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.272: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.272: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.273: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.273: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.273: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.273: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.273: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.273: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.273: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.273: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.274: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.274: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.274: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.274: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.274: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.274: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.274: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.274: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.275: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.275: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.275: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.275: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.275: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.275: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.275: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.275: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.276: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.276: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.276: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.276: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.276: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.276: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.276: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.276: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.277: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.277: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.277: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.277: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.277: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.277: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.278: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.278: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.278: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.278: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.278: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.278: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.278: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.278: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.279: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.279: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.279: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.279: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.279: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.279: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.279: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.279: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.280: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.280: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.281: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.281: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.281: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.281: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.281: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.281: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.281: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.281: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.282: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.282: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.282: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.282: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.282: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.282: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.282: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.282: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.283: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.283: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.283: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.283: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.283: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.283: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.284: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.284: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.284: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.284: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.284: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.284: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.284: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.284: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.285: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.285: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.285: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.285: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.285: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.285: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.285: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.285: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.286: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.286: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.286: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.286: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.286: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.286: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.286: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.286: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.287: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.287: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.288: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.288: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.288: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.288: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.288: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.288: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.288: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.288: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.289: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.289: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.289: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.289: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.289: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.289: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.289: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.289: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.290: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.290: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.290: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.290: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.290: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.290: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.291: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.291: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.291: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.291: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.291: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.291: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.291: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.291: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.292: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.292: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.292: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.292: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.292: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.292: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.292: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.292: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.293: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.293: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.293: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.293: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.293: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.293: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.293: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.293: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.294: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.294: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.295: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.295: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.295: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.295: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.295: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.295: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.295: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.295: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.296: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.296: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.296: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.296: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.296: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.296: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.296: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.297: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.297: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.297: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.297: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.297: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.297: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.297: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.298: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.298: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.298: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.298: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.298: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.298: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.298: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.298: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.299: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.299: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.300: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.300: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.300: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.300: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.300: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.300: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.300: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.300: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.301: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.301: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.301: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.301: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.301: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.301: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.301: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.301: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.302: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.302: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.302: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.302: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.302: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.302: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.302: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.302: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.303: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.303: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.303: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.303: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.303: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.303: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.304: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.304: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.304: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.304: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.304: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.304: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.304: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.304: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.305: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.305: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.305: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.305: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.305: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.305: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.305: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.305: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.306: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.306: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.307: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.307: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.307: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.307: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.307: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.307: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.307: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.307: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.308: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.308: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.308: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.308: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.308: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.308: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.308: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.308: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.309: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.309: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.309: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.309: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.309: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.309: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.310: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.310: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.310: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.310: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.310: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.310: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.310: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.310: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.311: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.311: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.311: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.311: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.311: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.311: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.311: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.311: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.312: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.312: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.313: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.313: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.313: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.313: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.313: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.313: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.314: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.314: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.314: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.314: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.314: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.314: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.314: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.314: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.315: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.315: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.315: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.315: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.316: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.316: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.316: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.316: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.316: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.316: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.317: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.317: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.317: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.317: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.317: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.317: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.317: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.317: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.318: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.318: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.318: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.318: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.318: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.318: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.318: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.318: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.319: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.319: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.319: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.319: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.319: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.319: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.319: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.319: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.320: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.320: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.320: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.320: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.320: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.320: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.321: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.321: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.321: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.321: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.321: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.321: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.321: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.321: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.322: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.322: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.323: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.323: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.323: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.323: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.323: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.323: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.323: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.323: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.324: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.324: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.324: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.324: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.324: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.324: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.324: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.324: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.325: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.325: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.325: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.325: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.325: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.325: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.326: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.326: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.326: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.326: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.326: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.326: [vfs7552] CAPTURE_NUM_STATES entering state 2 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.326: [vfs7552] REQUEST CHUNK entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.326: Sending vfs7552_read_image_chunk 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.327: [vfs7552] REQUEST CHUNK completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.327: [vfs7552] CAPTURE_NUM_STATES entering state 3 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.327: [vfs7552] CAPTURE_NUM_STATES entering state 2 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.327: [vfs7552] REQUEST CHUNK entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.327: Sending vfs7552_read_image_chunk 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.328: [vfs7552] REQUEST CHUNK completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.328: [vfs7552] CAPTURE_NUM_STATES entering state 3 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.328: [vfs7552] CAPTURE_NUM_STATES entering state 2 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.328: [vfs7552] REQUEST CHUNK entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.328: Sending vfs7552_read_image_chunk 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.329: [vfs7552] REQUEST CHUNK completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.329: [vfs7552] CAPTURE_NUM_STATES entering state 3 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.330: [vfs7552] CAPTURE_NUM_STATES entering state 4 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.330: Cleaning image 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.330: variance_after = 1737 142s 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.330: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.330: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.330: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.330: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.330: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.331: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.331: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.331: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.331: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.331: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.331: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.331: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.331: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.332: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.332: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.332: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.332: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.332: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.332: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.333: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.333: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.333: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.333: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.333: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.333: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.333: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.333: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.334: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.334: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.334: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.334: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.334: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.334: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.334: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.334: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.335: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.335: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.336: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.336: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.336: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.336: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.336: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.336: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.336: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.336: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.337: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.337: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.337: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.337: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.337: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.337: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.337: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.337: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.338: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.338: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.338: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.338: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.338: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.338: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.339: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.339: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.339: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.339: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.339: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.339: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.339: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.339: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.340: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.340: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.340: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.340: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.340: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.340: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.340: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.340: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.341: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.341: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.342: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.342: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.342: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.342: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.342: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.342: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.342: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.342: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.343: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.343: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.343: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.343: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.343: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.343: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.343: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.343: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.344: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.344: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.344: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.344: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.344: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.344: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.345: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.345: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.345: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.345: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.345: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.345: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.345: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.345: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.346: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.346: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.346: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.346: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.346: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.346: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.346: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.346: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.347: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.347: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.347: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.347: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.347: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.347: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.347: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.347: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.348: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.348: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.349: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.349: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.349: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.349: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.349: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.349: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.349: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.349: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.350: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.350: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.350: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.350: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.350: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.350: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.350: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.350: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.351: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.351: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.351: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.351: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.351: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.351: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.351: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.351: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.352: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.352: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.352: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.352: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.352: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.352: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.352: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.352: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.353: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.353: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.353: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.353: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.353: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.353: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.353: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.353: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.354: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.354: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.354: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.354: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.354: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.354: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.354: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.354: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.355: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.355: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.355: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.355: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.355: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.355: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.355: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.355: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.356: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.356: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.356: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.356: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.356: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.356: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.357: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.357: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.357: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.357: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.357: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.357: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.357: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.357: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.358: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.358: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.358: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.358: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.358: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.358: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.358: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.358: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.359: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.359: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.360: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.360: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.360: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.360: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.360: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.360: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.360: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.360: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.361: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.361: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.361: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.361: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.361: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.361: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.361: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.361: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.362: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.362: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.362: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.362: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.362: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.362: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.363: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.363: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.363: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.363: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.363: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.363: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.363: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.363: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.364: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.364: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.364: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.364: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.364: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.364: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.364: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.364: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.365: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.365: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.366: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.366: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.366: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.366: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.366: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.366: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.366: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.366: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.367: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.367: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.367: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.367: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.367: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.367: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.367: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.367: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.368: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.368: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.368: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.368: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.368: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.368: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.368: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.368: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.369: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.369: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.369: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.369: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.369: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.369: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.370: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.370: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.370: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.370: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.370: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.370: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.370: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.370: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.371: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.371: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.371: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.371: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.371: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.371: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.371: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.371: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.372: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.372: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.373: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.373: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.373: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.373: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.373: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.373: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.373: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.373: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.374: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.374: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.374: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.374: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.374: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.374: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.374: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.374: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.375: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.375: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.375: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.375: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.375: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.375: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.375: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.375: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.376: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.376: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.376: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.376: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.376: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.376: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.376: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.376: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.377: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.377: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.377: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.377: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.377: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.377: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.377: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.377: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.378: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.378: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.378: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.378: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.378: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.378: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.378: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.378: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.379: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.379: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.379: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.379: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.379: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.379: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.380: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.380: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.380: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.380: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.380: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.380: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.380: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.380: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.381: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.381: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.381: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.381: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.381: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.381: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.381: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.381: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.382: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.382: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.382: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.382: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.382: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.382: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.382: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.382: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.383: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.383: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.384: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.384: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.384: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.384: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.384: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.384: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.384: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.384: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.385: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.385: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.385: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.385: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.385: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.385: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.385: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.385: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.386: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.386: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.386: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.386: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.386: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.386: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.387: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.387: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.387: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.387: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.387: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.387: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.387: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.387: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.388: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.388: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.388: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.388: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.388: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.388: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.388: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.388: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.389: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.389: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.389: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.389: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.389: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.389: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.389: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.389: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.390: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.390: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.391: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.391: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.391: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.391: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.391: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.391: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.391: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.391: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.392: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.392: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.392: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.392: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.392: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.392: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.392: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.392: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.393: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.393: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.393: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.393: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.393: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.393: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.393: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.393: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.394: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.394: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.394: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.394: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.394: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.394: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.394: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.394: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.395: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.395: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.395: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.395: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.395: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.395: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.396: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.396: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.396: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.396: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.396: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.396: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.396: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.396: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.397: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.397: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.397: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.397: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.397: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.397: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.397: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.397: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.398: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.398: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.398: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.398: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.398: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.398: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.398: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.399: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.399: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.399: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.400: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.400: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.400: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.400: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.400: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.400: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.400: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.400: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.401: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.401: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.401: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.401: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.401: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.401: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.401: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.401: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.402: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.402: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.402: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.402: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.402: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.402: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.402: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.402: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.403: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.403: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.403: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.403: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.403: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.403: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.403: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.403: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.404: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.404: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.404: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.404: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.404: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.404: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.404: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.404: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.405: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.405: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.405: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.405: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.405: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.405: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.405: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.405: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.406: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.406: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.406: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.406: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.406: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.406: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.406: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.406: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.407: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.407: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.407: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.407: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.407: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.407: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.408: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.408: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.408: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.408: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.408: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.408: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.408: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.408: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.409: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.409: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.409: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.410: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.410: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.410: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.410: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.410: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.410: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.410: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.411: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.411: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.411: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.411: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.411: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.411: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.411: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.411: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.412: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.412: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.412: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.412: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.412: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.412: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.412: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.412: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.413: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.413: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.413: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.413: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.413: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.413: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.414: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.414: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.414: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.414: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.414: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.414: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.414: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.414: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.415: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.415: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.415: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.415: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.415: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.415: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.415: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.415: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.416: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.416: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.417: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.417: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.417: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.417: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.417: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.417: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.417: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.417: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.418: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.418: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.418: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.418: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.418: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.418: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.418: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.418: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.419: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.419: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.419: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.419: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.419: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.419: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.420: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.420: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.420: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.420: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.420: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.420: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.420: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.420: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.421: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.421: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.421: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.421: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.421: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.421: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.421: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.421: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.422: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.422: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.422: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.422: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.422: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.422: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.422: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.422: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.423: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.423: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.424: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.424: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.424: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.424: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.424: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.424: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.424: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.424: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.425: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.425: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.425: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.425: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.425: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.425: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.426: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.426: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.426: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.426: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.426: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.426: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.426: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.426: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.427: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.427: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.428: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.428: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.428: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.428: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.428: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.428: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.428: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.428: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.429: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.429: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.429: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.429: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.429: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.429: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.429: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.429: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.430: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.430: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.430: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.430: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.430: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.430: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.431: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.431: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.431: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.431: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.431: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.431: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.431: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.431: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.432: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.432: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.433: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.433: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.433: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.433: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.433: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.433: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.433: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.433: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.434: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.434: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.434: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.434: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.434: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.434: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.434: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.434: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.435: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.435: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.435: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.435: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.435: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.435: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.436: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.436: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.436: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.436: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.436: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.436: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.436: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.436: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.437: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.437: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.438: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.438: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.438: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.438: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.438: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.438: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.438: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.438: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.439: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.439: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.439: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.439: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.439: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.439: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.439: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.439: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.440: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.440: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.440: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.440: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.440: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.440: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.441: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.441: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.441: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.442: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.442: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.442: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.442: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.442: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.442: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.442: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.443: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.443: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.443: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.443: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.443: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.443: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.443: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.443: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.444: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.444: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.444: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.444: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.444: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.444: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.444: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.444: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.445: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.445: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.445: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.445: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.445: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.445: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.446: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.446: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.446: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.446: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.446: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.446: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.446: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.446: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.447: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.447: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.447: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.447: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.447: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.447: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.447: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.447: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.448: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.448: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.449: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.449: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.449: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.449: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.449: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.449: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.449: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.449: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.450: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.450: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.450: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.450: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.450: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.450: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.450: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.450: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.451: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.451: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.451: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.451: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.451: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.451: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.451: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.451: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.452: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.452: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.452: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.452: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.452: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.452: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.453: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.453: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.453: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.453: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.453: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.453: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.453: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.453: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.454: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.454: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.454: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.454: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.454: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.454: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.454: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.454: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.455: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.455: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.456: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.456: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.456: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.456: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.456: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.456: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.456: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.456: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.457: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.457: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.457: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.457: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.457: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.457: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.457: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.457: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.458: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.458: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.458: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.458: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.458: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.458: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.459: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.459: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.459: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.459: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.459: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.459: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.459: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.459: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.460: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.460: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.460: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.460: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.460: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.460: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.460: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.460: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.461: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.461: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.461: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.461: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.461: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.461: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.461: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.461: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.462: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.462: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.463: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.463: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.463: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.463: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.463: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.463: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.463: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.463: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.464: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.464: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.464: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.464: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.464: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.464: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.464: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.464: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.465: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.465: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.465: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.465: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.465: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.465: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.465: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.466: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.466: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.466: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.466: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.466: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.466: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.466: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.467: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.467: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.467: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.467: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.467: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.467: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.467: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.467: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.468: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.468: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.468: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.468: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.468: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.468: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.468: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.468: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.469: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.469: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.470: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.470: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.470: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.470: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.470: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.470: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.470: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.470: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.471: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.471: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.471: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.471: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.471: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.471: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.471: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.471: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.472: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.472: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.472: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.472: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.472: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.472: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.473: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.473: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.473: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.473: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.473: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.473: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.473: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.473: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.474: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.474: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.474: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.474: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.474: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.474: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.474: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.475: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.475: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.475: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.476: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.476: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.476: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.476: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.476: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.476: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.476: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.476: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.477: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.477: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.477: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.477: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.477: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.477: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.477: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.477: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.478: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.478: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.478: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.478: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.478: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.478: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.479: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.479: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.479: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.479: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.479: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.479: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.479: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.479: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.480: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.480: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.480: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.480: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.480: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.480: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.480: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.480: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.481: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.481: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.482: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.482: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.482: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.482: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.482: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.482: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.482: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.482: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.483: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.483: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.483: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.483: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.483: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.483: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.483: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.483: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.484: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.484: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.484: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.484: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.484: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.484: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.484: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.484: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.485: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.485: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.485: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.485: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.485: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.485: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.486: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.486: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.486: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.486: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.486: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.486: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.486: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.486: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.487: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.487: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.487: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.487: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.487: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.487: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.487: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.487: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.488: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.488: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.489: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.489: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.489: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.489: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.489: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.489: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.489: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.489: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.490: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.490: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.490: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.490: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.490: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.490: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.490: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.490: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.491: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.491: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.491: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.491: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.491: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.491: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.491: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.491: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.492: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.492: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.492: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.492: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.492: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.492: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.493: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.493: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.493: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.493: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.493: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.493: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.493: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.493: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.494: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.494: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.495: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.495: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.495: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.495: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.495: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.495: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.495: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.495: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.496: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.496: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.496: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.496: [vfs7552] CAPTURE_NUM_STATES entering state 2 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.496: [vfs7552] REQUEST CHUNK entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.496: Sending vfs7552_read_image_chunk 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.496: [vfs7552] REQUEST CHUNK completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.496: [vfs7552] CAPTURE_NUM_STATES entering state 3 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.497: [vfs7552] CAPTURE_NUM_STATES entering state 2 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.497: [vfs7552] REQUEST CHUNK entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.497: Sending vfs7552_read_image_chunk 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.498: [vfs7552] REQUEST CHUNK completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.498: [vfs7552] CAPTURE_NUM_STATES entering state 3 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.498: [vfs7552] CAPTURE_NUM_STATES entering state 2 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.498: [vfs7552] REQUEST CHUNK entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.498: Sending vfs7552_read_image_chunk 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.499: [vfs7552] REQUEST CHUNK completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.499: [vfs7552] CAPTURE_NUM_STATES entering state 3 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.499: [vfs7552] CAPTURE_NUM_STATES entering state 4 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.499: Cleaning image 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.499: variance_after = 1526 142s 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.499: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.499: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.499: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.500: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.500: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.501: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.501: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.501: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.501: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.501: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.501: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.501: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.501: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.502: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.502: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.502: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.502: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.502: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.502: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.502: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.502: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.503: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.503: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.503: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.503: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.503: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.503: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.503: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.503: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.504: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.504: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.504: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.504: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.504: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.504: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.505: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.505: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.505: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.505: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.505: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.505: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.505: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.505: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.506: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.506: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.507: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.507: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.507: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.507: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.507: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.507: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.507: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.507: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.508: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.508: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.508: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.508: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.508: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.508: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.508: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.508: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.509: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.509: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.509: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.509: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.509: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.509: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.510: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.510: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.510: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.510: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.510: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.510: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.510: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.510: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.511: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.511: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.511: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.511: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.511: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.511: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.511: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.511: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.512: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.512: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.512: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.513: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.513: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.513: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.513: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.513: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.513: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.513: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.514: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.514: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.514: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.514: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.514: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.514: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.514: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.514: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.515: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.515: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.515: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.515: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.515: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.515: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.515: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.515: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.516: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.516: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.516: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.516: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.516: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.516: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.516: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.516: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.517: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.517: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.517: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.517: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.517: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.517: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.518: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.518: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.518: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.518: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.518: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.518: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.518: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.518: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.519: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.519: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.520: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.520: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.520: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.520: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.520: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.520: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.520: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.520: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.521: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.521: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.521: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.521: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.521: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.521: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.521: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.521: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.522: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.522: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.522: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.522: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.522: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.522: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.522: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.522: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.523: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.523: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.523: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.523: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.523: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.523: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.523: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.523: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.524: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.524: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.524: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.524: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.524: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.524: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.524: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.524: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.525: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.525: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.525: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.525: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.525: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.525: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.525: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.525: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.526: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.526: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.526: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.526: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.526: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.526: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.527: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.527: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.527: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.527: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.527: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.527: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.527: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.527: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.528: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.528: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.528: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.528: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.528: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.528: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.528: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.528: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.529: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.529: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.530: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.530: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.530: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.530: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.530: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.530: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.530: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.530: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.531: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.531: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.531: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.531: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.531: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.531: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.531: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.531: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.532: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.532: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.532: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.532: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.532: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.532: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.532: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.532: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.533: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.533: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.533: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.533: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.533: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.533: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.534: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.534: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.534: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.534: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.534: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.534: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.534: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.534: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.535: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.535: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.536: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.536: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.536: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.536: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.536: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.536: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.536: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.536: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.537: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.537: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.537: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.537: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.537: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.537: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.537: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.537: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.538: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.538: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.538: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.538: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.538: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.538: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.538: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.538: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.539: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.539: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.539: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.539: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.539: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.539: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.540: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.540: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.540: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.540: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.540: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.540: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.540: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.540: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.541: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.541: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.541: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.541: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.541: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.541: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.541: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.541: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.542: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.542: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.542: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.542: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.542: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.542: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.542: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.543: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.543: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.543: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.544: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.544: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.544: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.544: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.544: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.544: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.544: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.544: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.545: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.545: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.545: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.545: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.545: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.545: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.545: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.545: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.546: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.546: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.546: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.546: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.546: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.546: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.546: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.546: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.547: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.547: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.547: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.547: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.547: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.547: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.548: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.548: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.548: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.548: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.548: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.548: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.548: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.548: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.549: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.549: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.549: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.549: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.549: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.549: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.549: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.549: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.550: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.550: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.550: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.550: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.550: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.550: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.550: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.550: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.551: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.551: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.551: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.551: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.551: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.551: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.551: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.551: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.552: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.552: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.552: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.552: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.552: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.552: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.553: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.553: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.553: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.553: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.553: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.553: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.553: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.553: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.554: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.554: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.554: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.554: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.555: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.555: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.555: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.555: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.555: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.555: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.555: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.555: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.556: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.556: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.556: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.556: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.556: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.556: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.557: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.557: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.557: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.557: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.557: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.557: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.557: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.557: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.558: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.558: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.558: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.558: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.558: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.558: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.558: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.558: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.559: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.559: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.559: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.559: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.559: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.559: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.559: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.559: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.560: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.560: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.560: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.560: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.560: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.560: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.560: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.560: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.561: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.561: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.561: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.561: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.561: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.561: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.561: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.561: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.562: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.562: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.563: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.563: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.563: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.563: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.563: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.563: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.563: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.563: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.564: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.564: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.564: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.564: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.564: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.564: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.564: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.564: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.565: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.565: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.565: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.565: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.565: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.565: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.565: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.565: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.566: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.566: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.566: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.566: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.566: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.566: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.567: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.567: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.567: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.567: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.567: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.567: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.567: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.567: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.568: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.568: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.568: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.568: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.568: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.568: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.568: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.568: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.569: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.569: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.570: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.570: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.570: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.570: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.570: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.570: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.570: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.570: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.571: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.571: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.571: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.571: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.571: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.571: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.571: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.571: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.572: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.572: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.572: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.572: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.572: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.572: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.572: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.572: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.573: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.573: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.573: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.573: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.573: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.573: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.574: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.574: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.574: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.574: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.574: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.574: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.574: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.574: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.575: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.575: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.575: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.575: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.575: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.575: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.575: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.575: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.576: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.576: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.577: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.577: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.577: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.577: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.577: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.577: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.577: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.577: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.578: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.578: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.578: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.578: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.578: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.578: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.578: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.578: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.579: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.579: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.579: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.579: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.579: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.579: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.579: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.579: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.580: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.580: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.580: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.580: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.580: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.580: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.580: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.580: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.581: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.581: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.581: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.581: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.581: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.581: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.582: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.582: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.582: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.582: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.582: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.582: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.582: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.582: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.583: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.583: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.583: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.583: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.583: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.583: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.583: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.583: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.584: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.584: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.584: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.584: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.584: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.584: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.584: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.584: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.585: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.585: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.585: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.585: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.585: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.585: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.585: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.585: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.586: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.586: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.587: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.587: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.587: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.587: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.587: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.587: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.587: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.587: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.588: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.588: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.588: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.588: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.588: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.588: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.588: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.588: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.589: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.589: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.589: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.589: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.589: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.589: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.589: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.589: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.590: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.590: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.590: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.590: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.590: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.590: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.591: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.591: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.591: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.591: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.591: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.591: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.591: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.591: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.592: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.592: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.592: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.592: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.592: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.592: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.592: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.592: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.593: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.593: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.593: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.593: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.593: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.593: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.593: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.593: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.593: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.593: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.594: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.594: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.594: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.594: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.594: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.594: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.595: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.595: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.596: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.596: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.596: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.596: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.596: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.596: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.596: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.596: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.597: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.597: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.597: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.597: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.597: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.597: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.597: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.597: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.598: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.598: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.598: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.598: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.598: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.598: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.599: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.599: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.599: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.599: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.599: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.599: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.599: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.599: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.600: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.600: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.600: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.600: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.600: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.600: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.600: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.600: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.601: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.601: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.601: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.601: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.601: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.601: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.601: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.601: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.602: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.602: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.602: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.602: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.602: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.602: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.602: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.602: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.603: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.603: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.604: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.604: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.604: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.604: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.604: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.604: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.604: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.604: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.605: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.605: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.605: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.605: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.605: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.605: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.605: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.605: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.606: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.606: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.606: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.606: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.606: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.606: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.606: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.606: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.607: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.607: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.607: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.607: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.607: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.607: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.607: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.608: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.608: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.608: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.608: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.608: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.608: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.608: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.609: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.609: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.609: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.609: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.609: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.609: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.609: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.609: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.610: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.610: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.610: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.610: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.610: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.610: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.610: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.610: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.611: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.611: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.611: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.611: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.611: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.611: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.611: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.611: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.612: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.612: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.612: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.612: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.612: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.612: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.612: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.612: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.613: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.613: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.613: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.613: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.613: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.613: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.613: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.613: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.614: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.614: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.614: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.614: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.614: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.614: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.614: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.614: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.615: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.615: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.616: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.616: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.616: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.616: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.616: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.616: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.616: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.616: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.617: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.617: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.617: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.617: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.617: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.617: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.617: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.617: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.618: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.618: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.618: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.618: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.618: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.618: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.618: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.618: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.619: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.619: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.619: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.619: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.619: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.619: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.619: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.619: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.620: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.620: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.620: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.620: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.620: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.620: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.621: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.621: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.621: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.621: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.621: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.621: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.621: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.621: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.622: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.622: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.622: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.622: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.622: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.622: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.622: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.622: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.623: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.623: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.623: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.623: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.623: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.623: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.623: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.623: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.624: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.624: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.624: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.624: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.624: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.624: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.624: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.624: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.625: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.625: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.626: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.626: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.626: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.626: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.626: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.626: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.626: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.626: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.627: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.627: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.627: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.627: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.627: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.627: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.627: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.627: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.628: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.628: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.628: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.628: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.628: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.628: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.628: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.628: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.629: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.629: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.629: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.629: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.629: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.629: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.630: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.630: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.630: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.630: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.630: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.630: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.630: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.630: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.631: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.631: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.631: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.631: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.631: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.631: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.631: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.631: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.632: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.632: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.632: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.632: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.632: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.632: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.632: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.632: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.633: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.633: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.633: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.633: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.633: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.633: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.633: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.633: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.634: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.634: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.635: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.635: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.635: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.635: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.635: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.635: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.635: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.635: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.636: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.636: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.636: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.636: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.636: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.636: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.636: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.636: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.637: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.637: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.637: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.637: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.637: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.637: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.637: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.637: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.638: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.638: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.638: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.638: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.638: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.638: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.638: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.638: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.639: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.639: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.639: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.639: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.639: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.639: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.640: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.640: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.640: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.640: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.640: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.640: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.640: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.640: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.641: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.641: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.641: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.641: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.641: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.641: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.641: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.641: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.642: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.642: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.642: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.642: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.642: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.642: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.642: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.642: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.643: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.643: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.643: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.643: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.643: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.643: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.643: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.643: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.644: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.644: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.645: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.645: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.645: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.645: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.645: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.645: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.645: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.645: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.645: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.645: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.645: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.646: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.646: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.646: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.646: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.646: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.646: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.646: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.646: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.646: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.646: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.646: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.647: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.647: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.647: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.647: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.647: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.647: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.647: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.647: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.648: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.648: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.648: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.648: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.648: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.648: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.648: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.649: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.649: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.649: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.649: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.649: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.649: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.649: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.650: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.650: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.650: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.650: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.651: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.651: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.651: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.651: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.651: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.651: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.651: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.651: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.652: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.652: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.652: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.652: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.652: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.652: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.652: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.652: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.653: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.653: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.653: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.653: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.653: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.653: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.653: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.653: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.654: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.654: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.654: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.654: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.654: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.654: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.654: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.654: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.655: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.655: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.655: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.655: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.655: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.655: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.655: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.655: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.656: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.656: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.656: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.656: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.656: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.656: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.656: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.656: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.657: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.657: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.657: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.657: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.657: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.657: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.657: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.657: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.658: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.658: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.658: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.658: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.658: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.658: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.658: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.658: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.659: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.659: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.659: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.659: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.659: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.659: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.659: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.659: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.660: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.660: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.660: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.660: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.660: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.660: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.661: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.661: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.661: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.661: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.661: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.661: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.661: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.661: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.662: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.662: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.662: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.662: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.662: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.662: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.662: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.662: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.663: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.663: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.664: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.664: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.664: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.664: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.664: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.664: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.664: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.664: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.665: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.665: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.665: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.665: [vfs7552] CAPTURE_NUM_STATES entering state 2 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.665: [vfs7552] REQUEST CHUNK entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.665: Sending vfs7552_read_image_chunk 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.665: [vfs7552] REQUEST CHUNK completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.665: [vfs7552] CAPTURE_NUM_STATES entering state 3 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.666: [vfs7552] CAPTURE_NUM_STATES entering state 2 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.666: [vfs7552] REQUEST CHUNK entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.666: Sending vfs7552_read_image_chunk 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.666: [vfs7552] REQUEST CHUNK completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.666: [vfs7552] CAPTURE_NUM_STATES entering state 3 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.667: [vfs7552] CAPTURE_NUM_STATES entering state 2 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.667: [vfs7552] REQUEST CHUNK entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.667: Sending vfs7552_read_image_chunk 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.667: [vfs7552] REQUEST CHUNK completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.667: [vfs7552] CAPTURE_NUM_STATES entering state 3 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.668: [vfs7552] CAPTURE_NUM_STATES entering state 4 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.668: Cleaning image 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.668: variance_after = 1435 142s 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.668: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.668: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.668: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.668: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.668: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.669: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.669: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.669: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.669: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.669: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.669: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.670: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.670: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.670: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.670: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.670: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.670: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.670: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.670: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.671: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.671: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.671: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.671: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.671: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.671: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.671: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.671: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.672: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.672: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.672: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.672: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.672: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.672: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.672: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.672: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.673: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.673: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.673: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.673: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.673: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.673: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.673: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.673: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.674: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.674: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.675: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.675: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.675: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.675: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.675: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.675: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.675: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.675: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.676: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.676: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.676: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.676: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.676: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.676: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.676: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.676: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.677: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.677: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.677: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.677: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.677: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.677: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.677: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.677: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.678: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.678: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.678: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.678: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.678: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.678: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.679: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.679: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.679: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.679: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.679: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.679: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.679: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.679: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.680: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.680: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.680: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.680: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.680: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.680: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.680: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.680: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.681: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.681: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.681: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.681: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.681: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.681: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.681: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.681: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.682: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.682: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.682: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.682: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.682: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.682: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.682: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.682: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.683: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.683: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.684: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.684: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.684: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.684: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.684: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.684: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.684: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.684: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.685: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.685: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.685: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.685: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.685: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.685: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.685: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.685: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.686: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.686: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.686: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.686: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.686: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.686: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.686: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.686: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.687: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.687: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.687: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.687: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.687: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.687: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.687: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.687: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.688: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.688: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.688: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.688: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.688: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.688: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.689: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.689: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.689: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.689: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.689: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.689: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.689: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.689: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.689: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.689: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.690: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.690: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.690: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.690: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.690: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.690: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.691: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.691: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.691: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.691: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.691: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.691: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.691: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.691: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.692: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.692: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.692: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.692: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.692: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.692: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.692: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.692: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.693: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.693: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.694: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.694: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.694: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.694: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.694: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.694: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.694: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.694: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.695: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.695: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.695: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.695: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.695: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.695: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.695: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.695: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.696: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.696: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.696: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.696: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.696: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.696: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.696: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.696: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.697: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.697: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.697: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.697: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.697: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.697: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.697: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.697: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.698: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.698: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.698: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.698: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.698: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.698: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.699: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.699: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.699: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.699: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.699: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.699: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.699: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.699: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.700: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.700: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.700: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.700: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.700: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.700: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.700: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.700: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.701: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.701: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.701: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.701: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.701: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.701: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.701: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.701: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.702: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.702: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.702: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.702: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.702: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.702: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.702: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.703: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.703: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.703: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.703: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.703: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.703: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.703: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.703: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.703: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.704: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.704: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.704: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.704: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.704: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.704: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.704: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.704: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.705: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.705: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.705: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.705: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.705: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.705: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.705: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.705: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.706: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.706: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.707: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.707: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.707: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.707: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.707: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.707: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.707: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.707: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.708: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.708: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.708: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.708: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.708: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.708: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.708: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.708: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.709: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.709: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.709: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.709: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.709: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.709: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.709: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.709: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.710: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.710: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.710: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.710: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.710: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.710: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.710: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.711: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.711: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.711: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.711: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.711: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.711: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.711: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.712: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.712: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.712: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.712: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.712: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.712: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.712: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.712: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.713: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.713: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.713: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.713: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.713: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.713: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.713: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.713: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.714: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.714: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.714: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.714: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.714: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.714: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.714: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.714: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.715: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.715: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.715: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.715: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.715: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.715: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.715: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.715: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.716: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.716: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.717: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.717: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.717: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.717: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.717: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.717: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.717: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.717: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.718: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.718: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.718: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.718: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.718: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.718: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.718: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.718: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.719: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.719: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.719: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.719: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.719: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.719: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.719: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.719: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.720: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.720: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.720: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.720: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.720: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.720: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.721: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.721: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.721: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.721: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.721: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.721: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.721: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.721: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.721: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.721: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.722: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.722: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.722: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.722: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.722: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.722: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.723: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.723: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.723: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.723: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.723: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.723: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.723: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.723: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.724: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.724: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.724: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.724: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.724: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.724: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.724: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.724: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.725: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.725: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.725: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.725: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.725: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.725: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.725: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.725: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.726: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.726: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.727: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.727: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.727: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.727: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.727: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.727: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.727: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.727: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.728: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.728: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.728: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.728: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.728: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.728: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.728: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.728: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.729: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.729: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.729: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.729: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.729: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.729: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.729: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.729: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.730: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.730: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.730: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.730: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.730: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.730: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.731: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.731: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.731: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.731: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.731: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.731: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.731: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.731: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.732: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.732: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.732: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.732: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.732: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.732: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.732: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.732: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.733: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.733: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.733: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.733: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.734: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.734: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.734: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.734: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.734: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.734: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.735: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.735: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.735: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.735: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.735: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.735: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.735: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.735: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.736: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.736: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.736: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.736: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.736: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.736: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.736: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.736: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.737: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.737: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.737: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.737: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.737: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.737: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.737: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.737: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.738: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.738: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.738: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.738: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.738: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.738: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.738: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.738: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.739: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.739: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.739: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.739: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.739: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.739: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.740: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.740: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.740: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.740: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.740: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.740: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.740: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.740: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.741: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.741: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.741: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.741: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.741: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.741: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.741: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.741: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.742: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.742: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.742: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.742: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.742: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.742: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.742: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.742: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.743: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.743: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.743: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.743: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.743: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.743: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.743: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.743: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.744: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.744: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.744: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.744: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.744: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.744: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.744: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.744: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.745: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.745: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.745: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.745: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.745: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.745: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.745: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.745: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.746: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.746: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.747: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.747: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.747: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.747: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.747: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.747: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.747: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.747: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.748: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.748: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.748: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.748: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.748: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.748: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.748: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.748: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.749: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.749: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.749: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.749: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.749: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.749: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.749: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.749: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.750: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.750: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.750: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.750: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.750: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.750: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.750: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.750: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.751: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.751: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.751: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.751: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.751: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.751: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.752: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.752: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.752: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.752: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.752: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.752: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.752: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.752: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.753: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.753: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.753: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.753: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.753: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.753: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.753: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.753: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.754: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.754: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.755: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.755: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.755: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.755: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.755: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.755: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.755: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.755: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.756: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.756: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.756: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.756: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.756: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.756: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.756: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.756: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.757: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.757: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.757: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.757: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.757: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.757: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.757: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.757: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.758: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.758: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.758: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.758: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.758: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.758: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.758: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.758: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.759: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.759: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.759: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.759: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.759: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.759: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.760: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.760: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.760: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.760: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.760: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.760: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.760: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.760: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.761: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.761: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.761: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.761: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.761: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.761: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.761: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.761: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.762: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.762: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.762: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.762: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.762: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.762: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.762: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.762: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.763: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.763: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.763: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.763: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.763: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.763: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.763: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.763: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.764: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.764: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.764: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.764: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.764: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.764: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.764: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.764: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.765: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.765: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.766: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.766: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.766: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.766: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.766: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.766: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.766: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.766: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.767: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.767: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.767: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.767: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.767: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.767: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.767: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.767: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.768: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.768: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.768: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.768: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.768: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.768: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.768: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.768: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.769: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.769: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.769: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.769: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.769: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.769: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.769: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.769: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.770: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.770: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.770: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.770: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.770: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.770: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.771: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.771: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.771: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.771: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.771: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.771: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.771: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.771: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.772: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.772: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.772: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.772: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.772: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.772: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.772: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.772: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.773: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.773: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.773: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.773: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.773: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.773: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.773: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.773: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.774: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.774: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.775: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.775: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.775: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.775: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.775: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.775: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.775: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.775: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.776: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.776: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.776: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.776: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.776: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.776: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.776: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.776: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.777: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.777: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.777: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.777: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.777: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.777: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.777: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.777: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.778: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.778: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.778: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.778: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.778: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.778: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.779: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.779: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.779: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.779: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.779: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.779: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.779: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.779: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.780: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.780: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.780: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.780: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.780: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.780: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.780: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.780: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.781: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.781: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.781: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.781: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.781: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.781: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.781: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.781: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.782: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.782: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.782: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.782: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.782: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.782: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.782: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.782: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.783: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.783: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.783: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.783: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.783: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.783: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.783: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.783: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.784: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.784: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.785: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.785: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.785: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.785: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.785: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.785: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.785: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.785: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.786: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.786: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.786: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.786: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.786: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.786: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.786: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.786: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.787: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.787: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.787: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.787: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.787: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.787: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.787: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.787: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.788: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.788: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.788: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.788: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.788: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.788: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.788: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.788: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.789: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.789: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.789: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.789: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.789: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.789: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.789: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.789: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.790: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.790: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.790: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.790: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.790: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.790: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.791: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.791: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.791: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.791: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.791: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.791: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.791: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.791: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.791: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.791: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.792: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.792: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.792: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.792: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.792: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.792: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.793: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.793: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.793: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.793: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.793: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.793: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.793: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.793: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.794: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.794: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.794: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.794: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.794: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.794: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.794: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.794: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.794: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.795: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.795: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.795: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.795: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.795: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.795: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.795: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.795: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.795: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.796: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.796: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.796: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.796: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.796: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.796: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.797: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.797: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.797: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.797: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.797: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.797: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.797: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.797: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.798: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.798: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.798: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.798: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.798: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.798: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.798: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.798: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.799: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.799: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.799: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.799: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.799: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.799: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.799: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.799: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.800: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.800: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.801: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.801: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.801: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.801: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.801: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.801: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.801: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.801: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.802: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.802: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.802: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.802: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.802: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.802: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.802: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.802: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.803: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.803: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.803: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.803: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.803: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.803: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.803: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.803: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.804: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.804: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.804: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.804: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.804: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.804: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.804: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.804: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.805: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.805: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.805: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.805: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.805: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.805: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.806: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.806: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.806: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.806: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.806: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.806: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.806: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.806: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.807: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.807: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.807: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.807: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.807: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.807: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.807: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.807: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.807: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.808: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.808: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.808: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.808: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.808: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.808: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.808: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.809: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.809: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.809: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.809: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.809: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.809: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.809: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.809: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.810: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.810: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.810: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.810: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.810: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.810: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.810: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.810: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.811: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.811: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.811: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.811: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.811: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.811: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.811: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.811: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.812: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.812: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.813: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.813: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.813: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.813: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.813: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.813: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.813: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.813: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.814: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.814: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.814: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.814: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.814: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.814: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.814: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.814: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.815: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.815: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.815: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.815: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.815: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.815: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.815: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.815: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.816: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.816: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.816: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.816: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.816: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.816: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.816: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.816: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.817: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.817: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.817: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.817: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.817: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.817: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.817: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.817: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.818: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.818: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.818: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.818: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.818: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.818: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.818: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.818: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.819: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.819: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.819: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.819: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.819: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.819: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.820: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.820: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.820: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.820: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.820: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.820: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.820: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.820: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.821: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.821: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.821: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.821: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.821: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.821: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.821: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.821: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.822: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.822: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.822: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.822: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.822: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.822: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.822: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.822: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.823: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.823: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.823: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.823: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.823: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.823: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.823: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.823: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.824: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.824: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.824: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.824: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.824: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.824: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.824: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.824: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.825: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.825: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.825: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.825: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.825: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.825: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.825: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.825: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.826: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.826: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.826: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.826: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.826: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.826: [vfs7552] CAPTURE_NUM_STATES entering state 2 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.826: [vfs7552] REQUEST CHUNK entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.826: Sending vfs7552_read_image_chunk 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.827: [vfs7552] REQUEST CHUNK completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.827: [vfs7552] CAPTURE_NUM_STATES entering state 3 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.827: [vfs7552] CAPTURE_NUM_STATES entering state 2 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.827: [vfs7552] REQUEST CHUNK entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.827: Sending vfs7552_read_image_chunk 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.828: [vfs7552] REQUEST CHUNK completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.828: [vfs7552] CAPTURE_NUM_STATES entering state 3 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.828: [vfs7552] CAPTURE_NUM_STATES entering state 2 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.828: [vfs7552] REQUEST CHUNK entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.828: Sending vfs7552_read_image_chunk 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.829: [vfs7552] REQUEST CHUNK completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.829: [vfs7552] CAPTURE_NUM_STATES entering state 3 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.830: [vfs7552] CAPTURE_NUM_STATES entering state 4 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.830: Cleaning image 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.830: variance_after = 1425 142s 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.830: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.830: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.830: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.830: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.830: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.831: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.831: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.831: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.831: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.831: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.831: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.831: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.831: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.832: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.832: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.832: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.832: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.832: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.832: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.832: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.832: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.833: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.833: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.833: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.833: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.833: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.833: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.833: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.833: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.834: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.834: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.834: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.834: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.834: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.834: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.834: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.834: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.835: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.835: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.835: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.835: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.835: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.835: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.835: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.835: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.836: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.836: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.836: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.836: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.836: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.836: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.837: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.837: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.837: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.837: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.837: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.837: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.837: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.837: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.838: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.838: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.838: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.838: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.838: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.838: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.838: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.838: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.839: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.839: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.839: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.839: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.839: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.839: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.839: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.839: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.840: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.840: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.841: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.841: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.841: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.841: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.841: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.841: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.841: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.841: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.842: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.842: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.842: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.842: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.842: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.842: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.842: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.842: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.843: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.843: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.843: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.843: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.843: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.843: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.843: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.843: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.844: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.844: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.844: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.844: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.844: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.844: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.844: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.844: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.845: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.845: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.845: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.845: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.845: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.845: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.845: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.845: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.846: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.846: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.846: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.846: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.846: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.846: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.846: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.846: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.847: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.847: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.847: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.847: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.847: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.847: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.847: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.847: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.848: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.848: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.848: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.848: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.848: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.848: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.848: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.848: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.849: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.849: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.849: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.849: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.849: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.849: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.850: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.850: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.850: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.850: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.850: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.850: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.850: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.850: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.851: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.851: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.851: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.851: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.851: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.851: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.851: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.851: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.852: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.852: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.852: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.852: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.852: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.852: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.852: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.852: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.853: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.853: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.853: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.853: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.853: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.853: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.853: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.853: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.854: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.854: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.854: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.854: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.854: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.854: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.854: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.854: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.855: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.855: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.855: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.855: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.855: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.855: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.855: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.855: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.856: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.856: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.857: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.857: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.857: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.857: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.857: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.857: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.857: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.857: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.858: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.858: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.858: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.858: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.858: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.858: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.858: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.858: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.859: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.859: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.859: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.859: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.859: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.859: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.859: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.859: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.860: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.860: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.860: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.860: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.860: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.860: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.860: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.860: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.861: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.861: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.861: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.861: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.861: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.861: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.862: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.862: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.862: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.862: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.862: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.862: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.862: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.862: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.863: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.863: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.863: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.863: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.863: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.863: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.863: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.863: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.864: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.864: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.864: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.864: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.864: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.864: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.864: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.864: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.865: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.865: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.865: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.865: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.865: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.865: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.865: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.865: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.866: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.866: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.866: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.866: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.866: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.866: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.866: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.866: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.867: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.867: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.867: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.867: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.867: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.867: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.867: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.868: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.868: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.868: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.869: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.869: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.869: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.869: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.869: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.869: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.869: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.869: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.870: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.870: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.870: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.870: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.870: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.870: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.870: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.870: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.871: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.871: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.871: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.871: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.871: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.871: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.871: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.871: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.872: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.872: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.872: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.872: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.872: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.872: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.872: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.872: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.873: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.873: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.873: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.873: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.873: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.873: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.874: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.874: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.874: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.874: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.874: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.874: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.874: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.874: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.875: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.875: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.875: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.875: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.875: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.875: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.875: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.875: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.876: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.876: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.876: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.876: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.876: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.876: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.876: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.876: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.877: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.877: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.878: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.878: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.878: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.878: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.878: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.878: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.878: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.878: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.879: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.879: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.879: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.879: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.879: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.879: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.879: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.879: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.880: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.880: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.880: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.880: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.880: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.880: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.880: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.880: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.881: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.881: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.881: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.881: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.881: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.881: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.881: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.881: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.882: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.882: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.882: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.882: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.882: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.882: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.882: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.882: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.883: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.883: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.883: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.883: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.883: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.883: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.884: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.884: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.884: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.884: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.884: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.884: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.884: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.884: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.885: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.885: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.885: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.885: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.885: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.885: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.885: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.885: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.886: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.886: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.886: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.886: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.886: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.886: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.886: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.886: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.887: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.887: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.887: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.887: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.887: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.887: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.887: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.887: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.888: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.888: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.888: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.888: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.888: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.888: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.888: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.888: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.889: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.889: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.889: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.889: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.889: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.889: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.889: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.889: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.890: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.890: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.890: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.890: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.890: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.890: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.890: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.890: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.891: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.891: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.892: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.892: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.892: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.892: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.892: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.892: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.892: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.892: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.893: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.893: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.893: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.893: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.893: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.893: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.893: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.893: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.894: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.894: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.894: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.894: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.894: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.894: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.894: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.894: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.895: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.895: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.895: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.895: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.895: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.895: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.895: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.895: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.896: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.896: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.896: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.896: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.896: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.896: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.897: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.897: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.897: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.897: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.897: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.897: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.897: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.897: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.898: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.898: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.898: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.898: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.898: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.898: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.898: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.898: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.899: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.899: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.899: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.899: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.899: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.899: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.899: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.899: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.900: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.900: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.900: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.900: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.900: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.900: [vfs7552] CAPTURE_NUM_STATES entering state 2 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.900: [vfs7552] REQUEST CHUNK entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.900: Sending vfs7552_read_image_chunk 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.901: [vfs7552] REQUEST CHUNK completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.901: [vfs7552] CAPTURE_NUM_STATES entering state 3 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.902: [vfs7552] CAPTURE_NUM_STATES entering state 2 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.902: [vfs7552] REQUEST CHUNK entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.902: Sending vfs7552_read_image_chunk 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.902: [vfs7552] REQUEST CHUNK completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.902: [vfs7552] CAPTURE_NUM_STATES entering state 3 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.903: [vfs7552] CAPTURE_NUM_STATES entering state 2 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.903: [vfs7552] REQUEST CHUNK entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.903: Sending vfs7552_read_image_chunk 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.903: [vfs7552] REQUEST CHUNK completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.903: [vfs7552] CAPTURE_NUM_STATES entering state 3 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.904: [vfs7552] CAPTURE_NUM_STATES entering state 4 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.904: Cleaning image 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.904: variance_after = 1532 142s 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.904: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.904: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.904: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.904: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.904: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.905: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.905: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.905: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.905: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.905: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.905: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.905: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.905: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.906: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.906: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.906: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.906: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.906: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.906: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.906: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.906: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.907: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.907: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.907: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.907: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.907: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.907: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.907: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.907: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.908: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.908: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.908: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.908: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.908: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.908: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.908: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.908: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.909: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.909: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.909: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.909: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.909: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.909: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.909: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.909: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.910: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.910: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.910: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.910: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.910: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.910: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.910: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.910: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.911: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.911: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.911: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.911: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.911: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.911: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.911: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.911: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.912: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.912: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.912: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.912: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.912: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.912: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.913: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.913: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.913: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.913: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.913: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.913: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.913: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.913: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.914: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.914: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.914: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.914: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.914: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.914: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.914: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.914: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.915: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.915: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.915: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.915: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.915: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.915: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.916: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.916: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.916: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.916: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.917: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.917: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.917: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.917: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.917: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.917: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.917: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.917: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.918: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.918: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.918: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.918: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.918: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.918: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.918: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.918: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.919: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.919: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.919: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.919: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.919: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.919: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.919: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.919: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.920: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.920: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.920: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.920: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.920: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.920: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.920: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.920: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.921: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.921: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.921: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.921: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.921: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.921: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.921: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.921: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.922: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.922: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.922: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.922: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.922: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.922: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.922: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.922: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.923: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.923: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.923: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.923: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.923: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.923: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.923: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.923: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.924: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.924: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.924: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.924: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.924: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.924: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.925: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.925: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.925: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.925: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.925: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.925: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.925: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.925: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.926: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.926: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.927: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.927: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.927: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.927: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.927: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.927: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.927: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.927: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.928: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.928: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.928: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.928: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.928: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.928: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.928: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.928: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.929: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.929: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.929: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.929: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.929: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.929: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.930: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.930: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.930: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.930: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.930: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.930: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.930: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.930: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.931: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.931: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.931: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.931: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.931: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.931: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.931: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.931: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.932: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.932: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.932: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.932: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.932: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.932: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.932: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.932: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.933: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.933: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.933: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.933: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.933: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.933: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.933: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.933: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.934: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.934: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.935: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.935: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.935: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.935: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.935: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.935: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.935: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.935: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.936: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.936: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.936: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.936: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.936: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.936: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.936: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.936: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.937: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.937: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.937: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.937: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.937: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.937: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.937: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.937: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.938: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.938: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.938: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.938: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.938: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.938: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.938: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.938: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.939: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.939: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.939: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.939: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.939: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.939: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.939: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.939: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.940: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.940: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.940: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.940: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.940: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.940: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.940: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.940: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.941: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.941: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.941: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.941: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.941: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.941: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.942: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.942: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.942: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.942: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.942: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.942: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.942: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.942: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.943: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.943: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.943: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.943: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.943: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.943: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.943: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.943: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.944: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.944: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.944: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.944: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.944: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.944: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.945: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.945: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.945: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.945: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.945: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.945: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.945: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.945: [vfs7552] CAPTURE_NUM_STATES entering state 2 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.945: [vfs7552] REQUEST CHUNK entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.945: Sending vfs7552_read_image_chunk 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.946: [vfs7552] REQUEST CHUNK completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.946: [vfs7552] CAPTURE_NUM_STATES entering state 3 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.947: [vfs7552] CAPTURE_NUM_STATES entering state 2 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.947: [vfs7552] REQUEST CHUNK entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.947: Sending vfs7552_read_image_chunk 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.947: [vfs7552] REQUEST CHUNK completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.947: [vfs7552] CAPTURE_NUM_STATES entering state 3 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.948: [vfs7552] CAPTURE_NUM_STATES entering state 2 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.948: [vfs7552] REQUEST CHUNK entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.948: Sending vfs7552_read_image_chunk 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.948: [vfs7552] REQUEST CHUNK completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.948: [vfs7552] CAPTURE_NUM_STATES entering state 3 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.949: [vfs7552] CAPTURE_NUM_STATES entering state 4 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.949: Cleaning image 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.949: variance_after = 1691 142s 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.949: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.949: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.949: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.949: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.949: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.950: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.950: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.950: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.950: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.950: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.950: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.950: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.950: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.951: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.951: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.951: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.951: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.951: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.951: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.952: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.952: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.952: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.952: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.952: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.952: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.952: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.952: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.953: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.953: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.953: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.953: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.953: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.953: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.953: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.953: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.954: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.954: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.954: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.954: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.954: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.954: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.954: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.954: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.955: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.955: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.955: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.955: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.955: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.955: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.955: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.955: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.956: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.956: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.957: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.957: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.957: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.957: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.957: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.957: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.957: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.957: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.958: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.958: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.958: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.958: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.958: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.958: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.958: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.958: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.959: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.959: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.959: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.959: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.959: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.959: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.959: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.959: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.960: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.960: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.960: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.960: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.960: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.960: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.961: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.961: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.961: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.961: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.961: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.961: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.961: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.961: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.962: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.962: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.962: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.962: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.962: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.962: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.962: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.962: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.963: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.963: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.963: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.963: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.963: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.963: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.963: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.963: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.964: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.964: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.964: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.964: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.964: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.964: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.964: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.964: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.965: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.965: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.965: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.965: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.965: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.965: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.965: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.965: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.966: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.966: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.966: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.966: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.966: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.966: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.966: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.966: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.967: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.967: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.967: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.967: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.967: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.968: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.968: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.968: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.968: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.968: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.969: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.969: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.969: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.969: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.969: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.969: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.969: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.969: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.970: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.970: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.970: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.970: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.970: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.970: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.970: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.970: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.971: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.971: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.971: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.971: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.971: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.971: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.971: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.971: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.972: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.972: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.972: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.972: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.972: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.972: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.972: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.972: Receiving 64 bytes 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.973: Got 6 bytes out of 64 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.973: [vfs7552] QUERY DATA READY completed successfully 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.973: [vfs7552] CAPTURE_NUM_STATES entering state 1 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.973: [vfs7552] CAPTURE_NUM_STATES entering state 0 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.973: [vfs7552] QUERY DATA READY entering state 0 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.973: Sending vfs7552_is_image_ready 142s (process:4102): libfprint-SSM-DEBUG: 03:38:09.974: [vfs7552] QUERY DATA READY entering state 1 142s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.974: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.974: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.974: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.974: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.974: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.974: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.974: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.974: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.974: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.975: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.975: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.975: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.975: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.975: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.975: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.975: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.975: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.976: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.976: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.976: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.976: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.976: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.976: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.977: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.977: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.977: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.977: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.977: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.977: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.977: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.977: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.978: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.978: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.978: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.978: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.978: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.978: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.978: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.978: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.979: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.979: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.979: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.979: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.979: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.979: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.979: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.979: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.980: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.980: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.980: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.980: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.980: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.980: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.980: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.980: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.981: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.981: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.981: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.981: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.981: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.981: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.981: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.982: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.982: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.982: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.983: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.983: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.983: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.983: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.983: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.983: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.983: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.983: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.984: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.984: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.984: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.984: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.984: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.984: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.984: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.984: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.985: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.985: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.985: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.985: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.985: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.985: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.985: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.985: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.986: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.986: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.986: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.986: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.986: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.986: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.986: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.987: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.987: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.987: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.987: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.987: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.987: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.987: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.988: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.988: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.988: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.988: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.988: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.988: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.988: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.988: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.989: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.989: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.989: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.989: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.989: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.989: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.989: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.989: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.990: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.990: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.991: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.991: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.991: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.991: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.991: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.991: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.991: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.991: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.992: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.992: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.992: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.992: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.992: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.992: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.992: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.992: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.993: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.993: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.993: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.993: [vfs7552] CAPTURE_NUM_STATES entering state 2 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.993: [vfs7552] REQUEST CHUNK entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.993: Sending vfs7552_read_image_chunk 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.993: [vfs7552] REQUEST CHUNK completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.993: [vfs7552] CAPTURE_NUM_STATES entering state 3 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.994: [vfs7552] CAPTURE_NUM_STATES entering state 2 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.994: [vfs7552] REQUEST CHUNK entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.994: Sending vfs7552_read_image_chunk 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.994: [vfs7552] REQUEST CHUNK completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.994: [vfs7552] CAPTURE_NUM_STATES entering state 3 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.995: [vfs7552] CAPTURE_NUM_STATES entering state 2 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.995: [vfs7552] REQUEST CHUNK entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.995: Sending vfs7552_read_image_chunk 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.995: [vfs7552] REQUEST CHUNK completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.995: [vfs7552] CAPTURE_NUM_STATES entering state 3 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.996: [vfs7552] CAPTURE_NUM_STATES entering state 4 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.996: Cleaning image 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.996: variance_after = 1845 143s 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.996: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.996: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.996: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.996: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.996: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.997: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.997: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.997: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.997: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.997: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.997: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.997: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.997: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.998: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.998: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.998: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.998: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.998: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.998: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.998: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.998: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.999: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.999: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.999: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.999: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:09.999: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:09.999: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.000: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.000: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.000: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.000: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.000: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.000: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.000: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.000: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.001: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.001: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.001: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.001: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.001: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.001: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.001: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.001: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.002: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.002: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.002: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.002: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.002: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.002: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.002: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.002: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.003: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.003: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.003: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.003: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.003: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.003: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.003: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.003: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.004: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.004: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.005: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.005: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.005: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.005: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.005: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.005: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.005: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.005: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.006: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.006: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.006: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.006: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.006: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.006: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.006: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.006: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.007: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.007: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.007: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.007: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.007: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.007: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.008: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.008: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.008: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.008: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.008: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.008: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.008: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.008: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.009: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.009: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.009: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.009: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.009: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.009: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.009: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.009: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.010: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.010: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.010: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.010: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.010: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.011: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.011: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.011: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.011: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.011: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.012: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.012: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.012: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.012: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.012: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.012: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.012: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.012: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.013: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.013: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.013: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.013: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.013: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.013: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.014: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.014: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.014: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.014: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.014: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.014: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.014: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.014: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.015: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.015: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.015: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.015: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.015: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.015: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.015: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.015: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.016: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.016: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.016: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.016: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.016: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.016: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.016: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.016: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.017: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.017: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.018: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.018: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.018: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.018: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.018: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.018: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.018: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.018: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.019: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.019: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.019: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.019: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.019: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.019: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.019: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.019: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.020: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.020: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.020: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.020: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.020: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.020: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.021: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.021: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.021: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.021: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.021: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.021: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.021: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.021: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.022: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.022: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.022: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.022: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.022: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.022: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.022: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.022: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.023: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.023: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.023: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.023: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.023: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.023: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.023: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.023: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.024: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.024: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.025: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.025: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.025: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.025: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.025: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.025: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.025: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.025: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.026: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.026: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.026: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.026: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.026: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.026: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.026: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.026: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.027: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.027: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.027: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.027: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.027: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.027: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.028: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.028: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.028: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.028: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.028: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.028: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.028: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.028: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.029: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.029: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.029: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.029: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.029: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.029: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.029: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.029: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.030: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.030: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.030: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.030: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.030: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.030: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.030: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.030: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.031: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.031: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.032: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.032: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.032: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.032: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.032: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.032: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.032: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.032: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.033: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.033: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.033: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.033: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.033: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.033: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.034: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.034: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.034: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.034: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.034: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.034: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.034: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.034: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.035: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.035: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.036: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.036: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.036: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.036: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.036: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.036: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.036: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.036: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.037: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.037: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.037: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.037: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.037: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.037: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.037: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.037: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.038: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.038: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.038: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.038: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.038: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.038: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.039: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.039: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.039: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.039: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.039: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.039: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.039: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.039: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.040: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.040: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.040: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.040: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.040: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.040: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.040: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.040: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.041: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.041: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.042: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.042: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.042: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.042: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.042: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.042: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.042: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.042: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.043: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.043: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.043: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.043: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.043: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.043: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.043: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.043: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.044: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.044: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.044: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.044: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.044: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.044: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.045: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.045: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.045: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.045: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.045: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.045: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.045: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.045: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.046: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.046: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.047: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.047: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.047: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.047: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.047: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.047: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.047: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.047: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.048: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.048: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.048: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.048: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.048: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.048: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.048: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.048: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.049: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.049: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.049: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.049: [vfs7552] CAPTURE_NUM_STATES entering state 2 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.049: [vfs7552] REQUEST CHUNK entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.049: Sending vfs7552_read_image_chunk 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.049: [vfs7552] REQUEST CHUNK completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.049: [vfs7552] CAPTURE_NUM_STATES entering state 3 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.050: [vfs7552] CAPTURE_NUM_STATES entering state 2 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.050: [vfs7552] REQUEST CHUNK entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.050: Sending vfs7552_read_image_chunk 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.050: [vfs7552] REQUEST CHUNK completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.050: [vfs7552] CAPTURE_NUM_STATES entering state 3 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.051: [vfs7552] CAPTURE_NUM_STATES entering state 2 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.051: [vfs7552] REQUEST CHUNK entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.051: Sending vfs7552_read_image_chunk 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.052: [vfs7552] REQUEST CHUNK completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.052: [vfs7552] CAPTURE_NUM_STATES entering state 3 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.052: [vfs7552] CAPTURE_NUM_STATES entering state 4 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.052: Cleaning image 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.052: variance_after = 2342 143s 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.052: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.052: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.052: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.053: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.053: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.053: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.053: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.053: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.053: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.053: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.053: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.054: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.054: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.054: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.054: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.054: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.054: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.054: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.054: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.055: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.055: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.056: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.056: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.056: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.056: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.056: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.056: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.056: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.056: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.057: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.057: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.057: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.057: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.057: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.057: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.057: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.057: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.058: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.058: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.058: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.058: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.058: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.058: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.059: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.059: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.059: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.059: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.059: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.059: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.059: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.059: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.060: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.060: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.061: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.061: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.061: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.061: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.061: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.061: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.061: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.061: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.062: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.062: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.062: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.062: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.062: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.062: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.062: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.062: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.063: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.063: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.063: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.063: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.063: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.063: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.064: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.064: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.064: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.064: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.064: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.064: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.064: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.064: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.065: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.065: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.065: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.065: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.065: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.065: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.065: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.065: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.066: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.066: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.066: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.066: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.066: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.066: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.066: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.066: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.067: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.067: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.068: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.068: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.068: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.068: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.068: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.068: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.068: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.068: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.069: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.069: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.069: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.069: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.069: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.069: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.069: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.069: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.070: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.070: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.070: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.070: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.070: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.070: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.070: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.070: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.071: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.071: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.071: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.071: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.071: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.071: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.072: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.072: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.072: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.072: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.072: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.072: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.072: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.072: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.073: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.073: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.073: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.073: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.073: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.073: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.073: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.073: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.074: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.074: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.075: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.075: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.075: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.075: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.075: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.075: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.075: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.075: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.076: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.076: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.076: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.076: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.076: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.076: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.077: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.077: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.077: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.077: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.077: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.077: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.077: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.077: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.078: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.078: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.078: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.078: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.079: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.079: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.079: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.079: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.079: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.079: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.080: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.080: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.080: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.080: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.080: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.080: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.080: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.080: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.081: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.081: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.081: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.081: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.081: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.081: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.081: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.081: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.082: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.082: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.082: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.082: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.082: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.082: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.082: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.082: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.083: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.083: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.083: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.083: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.083: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.083: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.083: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.083: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.084: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.084: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.084: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.084: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.084: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.084: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.084: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.084: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.085: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.085: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.085: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.085: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.085: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.085: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.086: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.086: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.086: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.086: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.086: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.086: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.086: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.086: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.087: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.087: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.088: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.088: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.088: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.088: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.088: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.088: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.088: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.088: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.089: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.089: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.089: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.089: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.089: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.089: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.089: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.089: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.090: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.090: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.090: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.090: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.090: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.090: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.091: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.091: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.092: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.092: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.092: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.092: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.092: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.092: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.092: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.092: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.093: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.093: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.093: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.093: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.093: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.093: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.094: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.094: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.094: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.094: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.094: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.094: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.094: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.094: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.095: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.095: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.095: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.095: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.095: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.095: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.095: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.095: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.096: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.096: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.097: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.097: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.097: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.097: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.097: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.097: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.097: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.097: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.098: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.098: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.098: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.098: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.098: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.098: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.098: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.098: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.099: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.099: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.099: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.099: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.099: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.099: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.100: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.100: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.100: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.100: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.100: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.100: [vfs7552] CAPTURE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.100: [vfs7552] QUERY DATA READY entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.100: Sending vfs7552_is_image_ready 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.101: [vfs7552] QUERY DATA READY entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.101: Receiving 64 bytes 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.102: Got 6 bytes out of 64 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.102: [vfs7552] QUERY DATA READY completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.102: [vfs7552] CAPTURE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.102: [vfs7552] CAPTURE_NUM_STATES entering state 2 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.102: [vfs7552] REQUEST CHUNK entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.102: Sending vfs7552_read_image_chunk 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.102: [vfs7552] REQUEST CHUNK completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.102: [vfs7552] CAPTURE_NUM_STATES entering state 3 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.103: [vfs7552] CAPTURE_NUM_STATES entering state 2 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.103: [vfs7552] REQUEST CHUNK entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.103: Sending vfs7552_read_image_chunk 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.103: [vfs7552] REQUEST CHUNK completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.103: [vfs7552] CAPTURE_NUM_STATES entering state 3 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.104: [vfs7552] CAPTURE_NUM_STATES entering state 2 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.104: [vfs7552] REQUEST CHUNK entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.104: Sending vfs7552_read_image_chunk 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.104: [vfs7552] REQUEST CHUNK completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.104: [vfs7552] CAPTURE_NUM_STATES entering state 3 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.105: [vfs7552] CAPTURE_NUM_STATES entering state 4 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.105: Cleaning image 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.105: variance_after = 16 143s 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.105: [vfs7552] CAPTURE_NUM_STATES completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.105: [vfs7552] DEACTIVATE_NUM_STATES entering state 0 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.115: [vfs7552] DEACTIVATE_NUM_STATES entering state 1 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.115: [vfs7552] STOP CAPTURE entering state 0 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.115: Sending vfs7552_cmd_04 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.116: [vfs7552] STOP CAPTURE entering state 1 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.116: Receiving 64 bytes 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.116: [vfs7552] STOP CAPTURE entering state 2 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.116: Sending vfs7552_cmd_52 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.117: [vfs7552] STOP CAPTURE entering state 3 143s (process:4102): libfprint-vfs7552-DEBUG: 03:38:10.117: Receiving 64 bytes 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.117: [vfs7552] STOP CAPTURE completed successfully 143s (process:4102): libfprint-SSM-DEBUG: 03:38:10.117: [vfs7552] DEACTIVATE_NUM_STATES completed successfully 143s (process:4102): libfprint-device-DEBUG: 03:38:10.117: Device reported finger status change: FP_FINGER_STATUS_NONE 143s (process:4102): libfprint-image_device-DEBUG: 03:38:10.117: Image device reported finger status: off 143s (process:4102): libfprint-image_device-DEBUG: 03:38:10.117: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 143s (process:4102): libfprint-image_device-DEBUG: 03:38:10.117: Deactivating image device 143s (process:4102): libfprint-image_device-DEBUG: 03:38:10.117: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 143s (process:4102): libfprint-image_device-DEBUG: 03:38:10.117: Image device deactivation completed 143s (process:4102): libfprint-image_device-DEBUG: 03:38:10.117: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 143s (process:4102): libfprint-device-DEBUG: 03:38:10.117: Device reported capture completion 143s (process:4102): libfprint-device-DEBUG: 03:38:10.118: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 143s (process:4102): libfprint-device-DEBUG: 03:38:10.118: Updated temperature model after 3.10 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 143s (process:4102): libfprint-image_device-DEBUG: 03:38:10.118: Image device close completed 143s (process:4102): libfprint-device-DEBUG: 03:38:10.118: Device reported close completion 143s (process:4102): libfprint-device-DEBUG: 03:38:10.118: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 143s (process:4102): libfprint-device-DEBUG: 03:38:10.118: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 143s ** (umockdev-run:4098): DEBUG: 03:38:10.216: umockdev.vala:154: Removing test bed /tmp/umockdev.IFQE22 143s (umockdev-run:4098): GLib-DEBUG: 03:38:10.222: unsetenv() is not thread-safe and should not be used after threads are created 143s Comparing PNGs /tmp/libfprint-umockdev-test-b2rxzr4x/capture.png and /usr/share/installed-tests/libfprint-2/vfs7552/capture.png 143s PASS: libfprint-2/driver-vfs7552.test 143s Running test: libfprint-2/driver-elanspi.test 143s ** (umockdev-run:4111): DEBUG: 03:38:10.283: umockdev.vala:127: Created udev test bed /tmp/umockdev.IMS612 143s ** (umockdev-run:4111): DEBUG: 03:38:10.284: 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 143s ** (umockdev-run:4111): DEBUG: 03:38:10.284: 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) 143s ** (umockdev-run:4111): DEBUG: 03:38:10.285: umockdev.vala:1558: create_node_for_device: creating pty device /tmp/umockdev.IMS612/dev/spidev0.0: got pty /dev/pts/0 143s ** (umockdev-run:4111): DEBUG: 03:38:10.285: umockdev.vala:1579: create_node_for_device: creating ptymap symlink /tmp/umockdev.IMS612/dev/.ptymap/_dev_pts_0 143s ** (umockdev-run:4111): DEBUG: 03:38:10.285: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0/spi-ELAN7001:00 143s ** (umockdev-run:4111): DEBUG: 03:38:10.286: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0/spi-ELAN7001:00 (subsystem spi) 143s ** (umockdev-run:4111): DEBUG: 03:38:10.288: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0 143s ** (umockdev-run:4111): DEBUG: 03:38:10.289: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0 (subsystem spi_master) 143s ** (umockdev-run:4111): DEBUG: 03:38:10.291: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3 143s ** (umockdev-run:4111): DEBUG: 03:38:10.291: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3 (subsystem platform) 143s ** (umockdev-run:4111): DEBUG: 03:38:10.292: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1e.2 143s ** (umockdev-run:4111): DEBUG: 03:38:10.293: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1e.2 (subsystem pci) 143s ** (umockdev-run:4111): DEBUG: 03:38:10.295: 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 143s ** (umockdev-run:4111): DEBUG: 03:38:10.295: 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) 143s ** (umockdev-run:4111): DEBUG: 03:38:10.296: umockdev.vala:1558: create_node_for_device: creating pty device /tmp/umockdev.IMS612/dev/hidraw0: got pty /dev/pts/1 143s ** (umockdev-run:4111): DEBUG: 03:38:10.296: umockdev.vala:1579: create_node_for_device: creating ptymap symlink /tmp/umockdev.IMS612/dev/.ptymap/_dev_pts_1 143s ** (umockdev-run:4111): DEBUG: 03:38:10.296: 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 143s ** (umockdev-run:4111): DEBUG: 03:38:10.297: 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) 143s ** (umockdev-run:4111): DEBUG: 03:38:10.298: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00 143s ** (umockdev-run:4111): DEBUG: 03:38:10.298: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00 (subsystem i2c) 143s ** (umockdev-run:4111): DEBUG: 03:38:10.299: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1 143s ** (umockdev-run:4111): DEBUG: 03:38:10.299: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1 (subsystem i2c) 143s ** (umockdev-run:4111): DEBUG: 03:38:10.300: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1 143s ** (umockdev-run:4111): DEBUG: 03:38:10.300: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1 (subsystem platform) 143s ** (umockdev-run:4111): DEBUG: 03:38:10.301: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:15.1 143s ** (umockdev-run:4111): DEBUG: 03:38:10.301: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:15.1 (subsystem pci) 143s (umockdev-run:4111): GLib-GIO-DEBUG: 03:38:10.303: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 143s (process:4115): libfprint-context-DEBUG: 03:38:10.426: Initializing FpContext (libfprint version 1.94.8+tod1) 143s (process:4115): libfprint-tod-DEBUG: 03:38:10.426: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 143s (process:4115): libfprint-device-DEBUG: 03:38:10.430: Device reported probe completion 143s (process:4115): libfprint-device-DEBUG: 03:38:10.430: Completing action FPI_DEVICE_ACTION_PROBE in idle! 143s (process:4115): libfprint-device-DEBUG: 03:38:10.430: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s (process:4115): libfprint-elanspi-DEBUG: 03:38:10.430: 90238568: ../libfprint/drivers/elanspi.c:1562 143s (process:4115): libfprint-image_device-DEBUG: 03:38:10.431: Image device open completed 143s (process:4115): libfprint-device-DEBUG: 03:38:10.431: Device reported open completion 143s (process:4115): libfprint-device-DEBUG: 03:38:10.431: Completing action FPI_DEVICE_ACTION_OPEN in idle! 143s (process:4115): libfprint-device-DEBUG: 03:38:10.431: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s (process:4115): libfprint-device-DEBUG: 03:38:10.431: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s (process:4115): libfprint-image_device-DEBUG: 03:38:10.431: Activating image device 143s (process:4115): libfprint-image_device-DEBUG: 03:38:10.431: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.431: [elanspi] ELANSPI_INIT_NSTATES entering state 0 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.432: [elanspi] ELANSPI_INIT_NSTATES entering state 1 143s (process:4115): libfprint-elanspi-DEBUG: 03:38:10.432: got status 81 143s (process:4115): libfprint-elanspi-DEBUG: 03:38:10.432: sync hw reset 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.432: [elanspi] ELANSPI_INIT_NSTATES entering state 2 143s libfprint-Message: 03:38:10.431: Failed to read spidev block size, using 4096 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.436: [elanspi] ELANSPI_INIT_NSTATES entering state 3 143s (process:4115): libfprint-elanspi-DEBUG: 03:38:10.437: sw reset ok 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.437: [elanspi] ELANSPI_INIT_NSTATES entering state 4 143s (process:4115): libfprint-elanspi-DEBUG: 03:38:10.437: raw height = 96 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.438: [elanspi] ELANSPI_INIT_NSTATES entering state 5 143s (process:4115): libfprint-elanspi-DEBUG: 03:38:10.438: raw width = 96 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.438: [elanspi] ELANSPI_INIT_NSTATES entering state 6 143s (process:4115): libfprint-elanspi-DEBUG: 03:38:10.438: raw reg17 = 175 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.439: [elanspi] ELANSPI_INIT_NSTATES entering state 7 143s (process:4115): libfprint-elanspi-DEBUG: 03:38:10.439: raw version = 09 143s (process:4115): libfprint-elanspi-DEBUG: 03:38:10.439: after hardcoded lookup; 96x96, version 1 143s (process:4115): libfprint-elanspi-DEBUG: 03:38:10.439: found sensor ID 6 => [eFSA96SA] (96 x 96) 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.439: [elanspi] ELANSPI_INIT_NSTATES entering state 8 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.443: [elanspi] ELANSPI_INIT_NSTATES entering state 9 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.445: [elanspi] ELANSPI_INIT_NSTATES entering state 10 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.446: [elanspi] ELANSPI_INIT_NSTATES entering state 11 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.447: [elanspi] ELANSPI_INIT_NSTATES entering state 12 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.447: [elanspi] ELANSPI_INIT_NSTATES entering state 13 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.448: [elanspi] ELANSPI_INIT_NSTATES entering state 14 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.448: [elanspi] ELANSPI_INIT_NSTATES entering state 17 143s (process:4115): libfprint-elanspi-DEBUG: 03:38:10.448: got vcm mode = 2 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.449: [elanspi] ELANSPI_INIT_NSTATES entering state 18 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.449: [elanspi] ELANSPI_INIT_NSTATES entering state 19 143s (process:4115): libfprint-elanspi-DEBUG: 03:38:10.449: starting calibrate 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.449: [elanspi] old calibrate entering state 0 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.451: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.452: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.452: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.452: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.452: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.453: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.453: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.453: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.453: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.454: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.454: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.454: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.454: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.455: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.455: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.455: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.455: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.455: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.455: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.455: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.455: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.456: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.456: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.456: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.456: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.457: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.457: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.457: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.457: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.458: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.458: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.458: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.458: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.458: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.458: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.458: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.459: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.459: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.459: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.459: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.459: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.459: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.459: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.460: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.460: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.460: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.460: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.460: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.460: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.461: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.461: [elanspi] ELANSPI_WRTABLE_NSTATES completed successfully 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.461: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.521: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 143s (process:4115): libfprint-elanspi-DEBUG: 03:38:10.521: dac init is 0x29 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.522: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 143s (process:4115): libfprint-device-DEBUG: 03:38:10.531: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.582: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.583: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.659: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 143s (process:4115): libfprint-elanspi-DEBUG: 03:38:10.659: calibration ok, saving bg image 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.659: [elanspi] old calibrate completed successfully 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.659: [elanspi] ELANSPI_INIT_NSTATES entering state 20 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.659: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.750: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.750: [elanspi] ELANSPI_INIT_NSTATES entering state 21 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.750: [elanspi] ELANSPI_INIT_NSTATES completed successfully 143s (process:4115): libfprint-elanspi-DEBUG: 03:38:10.750: 90557924: ../libfprint/drivers/elanspi.c:1596 143s (process:4115): libfprint-image_device-DEBUG: 03:38:10.750: Image device activation completed 143s (process:4115): libfprint-image_device-DEBUG: 03:38:10.750: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 143s (process:4115): libfprint-image_device-DEBUG: 03:38:10.750: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.750: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 0 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.750: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.750: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 143s (process:4115): libfprint-elanspi-DEBUG: 03:38:10.750: started capturer 143s (process:4115): libfprint-device-DEBUG: 03:38:10.750: Device reported finger status change: FP_FINGER_STATUS_NEEDED 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.828: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.828: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 143s (process:4115): libfprint-elanspi-DEBUG: 03:38:10.829: stddev=933d, ip=40, is_fp=0, is_empty=2 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.829: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.829: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.926: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.926: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 143s (process:4115): libfprint-elanspi-DEBUG: 03:38:10.927: stddev=829d, ip=48, is_fp=0, is_empty=2 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.927: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 143s (process:4115): libfprint-SSM-DEBUG: 03:38:10.927: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.005: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.005: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 144s (process:4115): libfprint-elanspi-DEBUG: 03:38:11.005: stddev=1307d, ip=37, is_fp=0, is_empty=2 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.005: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.005: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.066: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.066: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 144s (process:4115): libfprint-elanspi-DEBUG: 03:38:11.067: stddev=1163d, ip=38, is_fp=0, is_empty=2 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.067: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.067: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.129: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.129: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 144s (process:4115): libfprint-elanspi-DEBUG: 03:38:11.129: stddev=960d, ip=43, is_fp=0, is_empty=2 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.129: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.129: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.189: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.189: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 144s (process:4115): libfprint-elanspi-DEBUG: 03:38:11.190: stddev=879d, ip=41, is_fp=0, is_empty=2 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.190: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.190: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 144s Executing: libfprint-2/driver-elanspi.test 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.251: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.251: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 144s (process:4115): libfprint-elanspi-DEBUG: 03:38:11.252: stddev=925d, ip=44, is_fp=0, is_empty=2 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.252: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.252: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.312: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.312: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 144s (process:4115): libfprint-elanspi-DEBUG: 03:38:11.313: stddev=1244d, ip=37, is_fp=0, is_empty=2 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.313: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.313: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.382: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.382: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 144s (process:4115): libfprint-elanspi-DEBUG: 03:38:11.383: stddev=709d, ip=48, is_fp=0, is_empty=2 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.383: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.383: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.439: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.439: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 144s (process:4115): libfprint-elanspi-DEBUG: 03:38:11.440: stddev=553d, ip=54, is_fp=0, is_empty=2 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.440: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.440: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.515: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.515: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 144s (process:4115): libfprint-elanspi-DEBUG: 03:38:11.516: stddev=904d, ip=44, is_fp=0, is_empty=2 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.516: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.516: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.602: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.602: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 144s (process:4115): libfprint-elanspi-DEBUG: 03:38:11.603: stddev=951d, ip=46, is_fp=0, is_empty=2 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.603: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.603: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.667: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.667: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 144s (process:4115): libfprint-elanspi-DEBUG: 03:38:11.668: stddev=795d, ip=44, is_fp=0, is_empty=2 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.668: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.668: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.743: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.743: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 144s (process:4115): libfprint-elanspi-DEBUG: 03:38:11.743: stddev=985d, ip=41, is_fp=0, is_empty=2 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.743: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.744: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.816: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.816: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 144s (process:4115): libfprint-elanspi-DEBUG: 03:38:11.817: stddev=938d, ip=40, is_fp=0, is_empty=2 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.817: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.817: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.891: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.891: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 144s (process:4115): libfprint-elanspi-DEBUG: 03:38:11.892: stddev=846d, ip=40, is_fp=0, is_empty=2 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.892: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.892: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.959: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.959: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 144s (process:4115): libfprint-elanspi-DEBUG: 03:38:11.959: stddev=693d, ip=56, is_fp=0, is_empty=2 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.959: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 144s (process:4115): libfprint-SSM-DEBUG: 03:38:11.959: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.030: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.030: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 145s (process:4115): libfprint-elanspi-DEBUG: 03:38:12.031: stddev=777d, ip=50, is_fp=0, is_empty=2 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.031: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.031: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.107: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.108: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 145s (process:4115): libfprint-elanspi-DEBUG: 03:38:12.108: stddev=824d, ip=45, is_fp=0, is_empty=2 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.108: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.108: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.176: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.177: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 145s (process:4115): libfprint-elanspi-DEBUG: 03:38:12.177: stddev=521d, ip=50, is_fp=0, is_empty=2 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.177: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.177: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.251: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.251: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 145s (process:4115): libfprint-elanspi-DEBUG: 03:38:12.252: stddev=670d, ip=47, is_fp=0, is_empty=2 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.252: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.252: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.354: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.355: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 145s (process:4115): libfprint-elanspi-DEBUG: 03:38:12.355: stddev=1262d, ip=39, is_fp=0, is_empty=2 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.355: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.355: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.424: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.424: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 145s (process:4115): libfprint-elanspi-DEBUG: 03:38:12.424: stddev=912d, ip=42, is_fp=0, is_empty=2 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.425: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.425: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.490: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.490: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 145s (process:4115): libfprint-elanspi-DEBUG: 03:38:12.491: stddev=1402d, ip=37, is_fp=0, is_empty=2 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.491: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.491: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.563: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.563: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 145s (process:4115): libfprint-elanspi-DEBUG: 03:38:12.564: stddev=1530d, ip=32, is_fp=0, is_empty=2 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.564: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.564: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.627: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.627: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 145s (process:4115): libfprint-elanspi-DEBUG: 03:38:12.628: stddev=718159d, ip=6, is_fp=1, is_empty=0 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.628: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.628: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.693: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.693: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 145s (process:4115): libfprint-elanspi-DEBUG: 03:38:12.694: stddev=400929d, ip=0, is_fp=2, is_empty=0 145s (process:4115): libfprint-device-DEBUG: 03:38:12.694: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 145s (process:4115): libfprint-image_device-DEBUG: 03:38:12.694: Image device reported finger status: on 145s (process:4115): libfprint-image_device-DEBUG: 03:38:12.694: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.694: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.694: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.759: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.759: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 145s (process:4115): libfprint-elanspi-DEBUG: 03:38:12.760: stddev=346514d, ip=0, is_fp=1, is_empty=0 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.761: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.761: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.838: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.838: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 145s (process:4115): libfprint-elanspi-DEBUG: 03:38:12.839: stddev=324160d, ip=0, is_fp=1, is_empty=0 145s (process:4115): libfprint-elanspi-DEBUG: 03:38:12.840: diff = 107344 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.840: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.840: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.914: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.914: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 145s (process:4115): libfprint-elanspi-DEBUG: 03:38:12.915: stddev=339430d, ip=0, is_fp=1, is_empty=0 145s (process:4115): libfprint-elanspi-DEBUG: 03:38:12.916: diff = 246471 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.916: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 145s (process:4115): libfprint-SSM-DEBUG: 03:38:12.916: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 146s (process:4115): libfprint-SSM-DEBUG: 03:38:12.982: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 146s (process:4115): libfprint-SSM-DEBUG: 03:38:12.982: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 146s (process:4115): libfprint-elanspi-DEBUG: 03:38:12.983: stddev=334711d, ip=0, is_fp=1, is_empty=0 146s (process:4115): libfprint-elanspi-DEBUG: 03:38:12.984: diff = 73010 146s (process:4115): libfprint-SSM-DEBUG: 03:38:12.984: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 146s (process:4115): libfprint-SSM-DEBUG: 03:38:12.984: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.050: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.051: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 146s (process:4115): libfprint-elanspi-DEBUG: 03:38:13.051: stddev=317574d, ip=0, is_fp=1, is_empty=0 146s (process:4115): libfprint-elanspi-DEBUG: 03:38:13.053: diff = 58831 146s (process:4115): libfprint-elanspi-DEBUG: 03:38:13.053: ignoring b.c. difference is too small 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.053: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.053: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.115: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.115: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 146s (process:4115): libfprint-elanspi-DEBUG: 03:38:13.116: stddev=285577d, ip=0, is_fp=1, is_empty=0 146s (process:4115): libfprint-elanspi-DEBUG: 03:38:13.117: diff = 241923 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.117: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.117: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.179: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.179: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 146s (process:4115): libfprint-elanspi-DEBUG: 03:38:13.180: stddev=417772d, ip=0, is_fp=2, is_empty=0 146s (process:4115): libfprint-elanspi-DEBUG: 03:38:13.181: diff = 254823 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.181: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.181: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.247: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.247: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 146s (process:4115): libfprint-elanspi-DEBUG: 03:38:13.248: stddev=541148d, ip=0, is_fp=2, is_empty=0 146s (process:4115): libfprint-elanspi-DEBUG: 03:38:13.249: diff = 290922 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.249: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.249: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.309: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.309: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 146s (process:4115): libfprint-elanspi-DEBUG: 03:38:13.310: stddev=580192d, ip=0, is_fp=2, is_empty=0 146s (process:4115): libfprint-elanspi-DEBUG: 03:38:13.311: diff = 332283 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.311: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.311: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.372: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.372: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 146s (process:4115): libfprint-elanspi-DEBUG: 03:38:13.373: stddev=484527d, ip=0, is_fp=2, is_empty=0 146s (process:4115): libfprint-elanspi-DEBUG: 03:38:13.374: diff = 325141 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.374: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.374: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.434: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.434: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 146s (process:4115): libfprint-elanspi-DEBUG: 03:38:13.435: stddev=482100d, ip=0, is_fp=2, is_empty=0 146s (process:4115): libfprint-elanspi-DEBUG: 03:38:13.436: diff = 337412 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.436: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.436: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.501: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.501: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 146s (process:4115): libfprint-elanspi-DEBUG: 03:38:13.502: stddev=558238d, ip=0, is_fp=2, is_empty=0 146s (process:4115): libfprint-elanspi-DEBUG: 03:38:13.503: diff = 342841 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.503: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.503: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.580: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.580: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 146s (process:4115): libfprint-elanspi-DEBUG: 03:38:13.581: stddev=572990d, ip=0, is_fp=2, is_empty=0 146s (process:4115): libfprint-elanspi-DEBUG: 03:38:13.582: diff = 352690 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.582: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.582: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.657: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.657: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 146s (process:4115): libfprint-elanspi-DEBUG: 03:38:13.658: stddev=575411d, ip=0, is_fp=2, is_empty=0 146s (process:4115): libfprint-elanspi-DEBUG: 03:38:13.659: diff = 365537 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.659: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.659: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.732: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.732: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 146s (process:4115): libfprint-elanspi-DEBUG: 03:38:13.732: stddev=578482d, ip=0, is_fp=2, is_empty=0 146s (process:4115): libfprint-elanspi-DEBUG: 03:38:13.734: diff = 342041 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.734: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.734: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.798: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.798: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 146s (process:4115): libfprint-elanspi-DEBUG: 03:38:13.799: stddev=572686d, ip=0, is_fp=2, is_empty=0 146s (process:4115): libfprint-elanspi-DEBUG: 03:38:13.800: diff = 421037 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.800: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.800: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.868: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.868: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 146s (process:4115): libfprint-elanspi-DEBUG: 03:38:13.869: stddev=465498d, ip=0, is_fp=2, is_empty=0 146s (process:4115): libfprint-elanspi-DEBUG: 03:38:13.870: diff = 404640 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.870: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.870: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.927: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.927: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 146s (process:4115): libfprint-elanspi-DEBUG: 03:38:13.928: stddev=410135d, ip=0, is_fp=2, is_empty=0 146s (process:4115): libfprint-elanspi-DEBUG: 03:38:13.929: diff = 347658 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.929: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 146s (process:4115): libfprint-SSM-DEBUG: 03:38:13.929: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 147s (process:4115): libfprint-SSM-DEBUG: 03:38:13.996: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 147s (process:4115): libfprint-SSM-DEBUG: 03:38:13.996: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 147s (process:4115): libfprint-elanspi-DEBUG: 03:38:13.997: stddev=493239d, ip=0, is_fp=2, is_empty=0 147s (process:4115): libfprint-elanspi-DEBUG: 03:38:13.998: diff = 344237 147s (process:4115): libfprint-SSM-DEBUG: 03:38:13.998: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 147s (process:4115): libfprint-SSM-DEBUG: 03:38:13.998: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 147s (process:4115): libfprint-SSM-DEBUG: 03:38:14.087: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 147s (process:4115): libfprint-SSM-DEBUG: 03:38:14.087: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 147s (process:4115): libfprint-elanspi-DEBUG: 03:38:14.088: stddev=553028d, ip=0, is_fp=2, is_empty=0 147s (process:4115): libfprint-elanspi-DEBUG: 03:38:14.090: diff = 419597 147s (process:4115): libfprint-SSM-DEBUG: 03:38:14.090: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 147s (process:4115): libfprint-SSM-DEBUG: 03:38:14.090: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 147s (process:4115): libfprint-SSM-DEBUG: 03:38:14.167: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 147s (process:4115): libfprint-SSM-DEBUG: 03:38:14.168: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 147s (process:4115): libfprint-elanspi-DEBUG: 03:38:14.168: stddev=574502d, ip=0, is_fp=2, is_empty=0 147s (process:4115): libfprint-elanspi-DEBUG: 03:38:14.170: diff = 408934 147s (process:4115): libfprint-SSM-DEBUG: 03:38:14.170: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 147s (process:4115): libfprint-SSM-DEBUG: 03:38:14.170: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 147s (process:4115): libfprint-SSM-DEBUG: 03:38:14.245: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 147s (process:4115): libfprint-SSM-DEBUG: 03:38:14.245: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 147s (process:4115): libfprint-elanspi-DEBUG: 03:38:14.245: stddev=645815d, ip=0, is_fp=2, is_empty=0 147s (process:4115): libfprint-elanspi-DEBUG: 03:38:14.247: diff = 409198 147s (process:4115): libfprint-SSM-DEBUG: 03:38:14.247: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 147s (process:4115): libfprint-SSM-DEBUG: 03:38:14.247: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 147s (process:4115): libfprint-SSM-DEBUG: 03:38:14.326: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 147s (process:4115): libfprint-SSM-DEBUG: 03:38:14.326: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 147s (process:4115): libfprint-elanspi-DEBUG: 03:38:14.327: stddev=677451d, ip=0, is_fp=2, is_empty=0 147s (process:4115): libfprint-elanspi-DEBUG: 03:38:14.328: diff = 429666 147s (process:4115): libfprint-SSM-DEBUG: 03:38:14.328: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 147s (process:4115): libfprint-SSM-DEBUG: 03:38:14.328: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 147s (process:4115): libfprint-SSM-DEBUG: 03:38:14.397: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 147s (process:4115): libfprint-SSM-DEBUG: 03:38:14.397: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 147s (process:4115): libfprint-elanspi-DEBUG: 03:38:14.398: stddev=634407d, ip=0, is_fp=2, is_empty=0 147s (process:4115): libfprint-elanspi-DEBUG: 03:38:14.398: have enough frames, exiting now 147s (process:4115): libfprint-assembling-DEBUG: 03:38:14.511: calc delta completed in 0.113549 secs 147s (process:4115): libfprint-assembling-DEBUG: 03:38:14.628: calc delta completed in 0.116546 secs 147s (process:4115): libfprint-assembling-DEBUG: 03:38:14.628: errors: 86516 rev: 170625 147s (process:4115): libfprint-assembling-DEBUG: 03:38:14.744: calc delta completed in 0.115741 secs 147s (process:4115): libfprint-assembling-DEBUG: 03:38:14.744: height is 246 147s (process:4115): libfprint-image_device-DEBUG: 03:38:14.745: Image device captured an image 147s (process:4115): libfprint-image_device-DEBUG: 03:38:14.745: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 147s (process:4115): libfprint-device-DEBUG: 03:38:14.745: Device reported finger status change: FP_FINGER_STATUS_PRESENT 147s (process:4115): libfprint-SSM-DEBUG: 03:38:14.745: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 147s (process:4115): libfprint-SSM-DEBUG: 03:38:14.746: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 147s (process:4115): libfprint-SSM-DEBUG: 03:38:14.804: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 147s (process:4115): libfprint-SSM-DEBUG: 03:38:14.804: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 147s (process:4115): libfprint-elanspi-DEBUG: 03:38:14.805: stddev=593525d, ip=0, is_fp=2, is_empty=0 147s (process:4115): libfprint-SSM-DEBUG: 03:38:14.805: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 147s (process:4115): libfprint-SSM-DEBUG: 03:38:14.805: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 147s (process:4115): libfprint-image-DEBUG: 03:38:14.825: Minutiae scan completed in 0.078904 secs 147s (process:4115): libfprint-SSM-DEBUG: 03:38:14.877: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 147s (process:4115): libfprint-SSM-DEBUG: 03:38:14.877: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 147s (process:4115): libfprint-elanspi-DEBUG: 03:38:14.878: stddev=610651d, ip=0, is_fp=2, is_empty=0 147s (process:4115): libfprint-SSM-DEBUG: 03:38:14.878: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 147s (process:4115): libfprint-SSM-DEBUG: 03:38:14.878: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 147s (process:4115): libfprint-SSM-DEBUG: 03:38:14.947: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 147s (process:4115): libfprint-SSM-DEBUG: 03:38:14.947: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 147s (process:4115): libfprint-elanspi-DEBUG: 03:38:14.948: stddev=505673d, ip=0, is_fp=2, is_empty=0 147s (process:4115): libfprint-SSM-DEBUG: 03:38:14.948: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 147s (process:4115): libfprint-SSM-DEBUG: 03:38:14.948: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.020: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.020: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 148s (process:4115): libfprint-elanspi-DEBUG: 03:38:15.020: stddev=537580d, ip=0, is_fp=2, is_empty=0 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.020: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.021: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.100: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.100: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 148s (process:4115): libfprint-elanspi-DEBUG: 03:38:15.101: stddev=520750d, ip=0, is_fp=2, is_empty=0 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.101: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.101: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.163: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.163: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 148s (process:4115): libfprint-elanspi-DEBUG: 03:38:15.164: stddev=468008d, ip=0, is_fp=2, is_empty=0 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.164: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.164: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.234: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.234: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 148s (process:4115): libfprint-elanspi-DEBUG: 03:38:15.234: stddev=477058d, ip=0, is_fp=2, is_empty=0 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.234: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.234: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.314: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.314: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 148s (process:4115): libfprint-elanspi-DEBUG: 03:38:15.314: stddev=460178d, ip=0, is_fp=2, is_empty=0 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.314: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.315: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.374: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.374: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 148s (process:4115): libfprint-elanspi-DEBUG: 03:38:15.375: stddev=538508d, ip=0, is_fp=2, is_empty=0 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.375: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.375: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.449: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.449: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 148s (process:4115): libfprint-elanspi-DEBUG: 03:38:15.450: stddev=661673d, ip=0, is_fp=2, is_empty=0 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.450: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.450: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.523: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.523: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 148s (process:4115): libfprint-elanspi-DEBUG: 03:38:15.524: stddev=764706d, ip=0, is_fp=2, is_empty=0 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.524: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.524: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.589: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.589: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 148s (process:4115): libfprint-elanspi-DEBUG: 03:38:15.590: stddev=806415d, ip=0, is_fp=2, is_empty=0 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.590: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.590: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.655: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.655: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 148s (process:4115): libfprint-elanspi-DEBUG: 03:38:15.656: stddev=806649d, ip=0, is_fp=2, is_empty=0 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.656: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.656: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.725: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.725: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 148s (process:4115): libfprint-elanspi-DEBUG: 03:38:15.726: stddev=822567d, ip=0, is_fp=2, is_empty=0 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.726: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.726: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.820: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.820: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 148s (process:4115): libfprint-elanspi-DEBUG: 03:38:15.821: stddev=1017068d, ip=0, is_fp=2, is_empty=0 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.821: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.821: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.896: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.896: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 148s (process:4115): libfprint-elanspi-DEBUG: 03:38:15.897: stddev=1004196d, ip=0, is_fp=2, is_empty=0 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.897: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.897: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.964: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.964: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 148s (process:4115): libfprint-elanspi-DEBUG: 03:38:15.965: stddev=963655d, ip=0, is_fp=2, is_empty=0 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.965: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 148s (process:4115): libfprint-SSM-DEBUG: 03:38:15.965: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 149s (process:4115): libfprint-SSM-DEBUG: 03:38:16.026: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 149s (process:4115): libfprint-SSM-DEBUG: 03:38:16.027: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 149s (process:4115): libfprint-elanspi-DEBUG: 03:38:16.027: stddev=880521d, ip=0, is_fp=2, is_empty=0 149s (process:4115): libfprint-SSM-DEBUG: 03:38:16.027: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 149s (process:4115): libfprint-SSM-DEBUG: 03:38:16.027: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 149s (process:4115): libfprint-SSM-DEBUG: 03:38:16.105: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 149s (process:4115): libfprint-SSM-DEBUG: 03:38:16.105: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 149s (process:4115): libfprint-elanspi-DEBUG: 03:38:16.106: stddev=1135372d, ip=0, is_fp=2, is_empty=0 149s (process:4115): libfprint-SSM-DEBUG: 03:38:16.106: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 149s (process:4115): libfprint-SSM-DEBUG: 03:38:16.106: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 149s (process:4115): libfprint-SSM-DEBUG: 03:38:16.178: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 149s (process:4115): libfprint-SSM-DEBUG: 03:38:16.178: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 149s (process:4115): libfprint-elanspi-DEBUG: 03:38:16.178: stddev=1093450d, ip=3, is_fp=1, is_empty=0 149s (process:4115): libfprint-SSM-DEBUG: 03:38:16.178: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 149s (process:4115): libfprint-SSM-DEBUG: 03:38:16.178: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 149s Executing: libfprint-2/driver-elanspi.test 149s (process:4115): libfprint-SSM-DEBUG: 03:38:16.278: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 149s (process:4115): libfprint-SSM-DEBUG: 03:38:16.278: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 149s (process:4115): libfprint-elanspi-DEBUG: 03:38:16.279: stddev=41090d, ip=8, is_fp=0, is_empty=2 149s (process:4115): libfprint-SSM-DEBUG: 03:38:16.279: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 149s (process:4115): libfprint-SSM-DEBUG: 03:38:16.279: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 149s (process:4115): libfprint-SSM-DEBUG: 03:38:16.371: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 149s (process:4115): libfprint-SSM-DEBUG: 03:38:16.371: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 149s (process:4115): libfprint-elanspi-DEBUG: 03:38:16.372: stddev=6836d, ip=13, is_fp=0, is_empty=2 149s (process:4115): libfprint-device-DEBUG: 03:38:16.372: Device reported finger status change: FP_FINGER_STATUS_NONE 149s (process:4115): libfprint-image_device-DEBUG: 03:38:16.372: Image device reported finger status: off 149s (process:4115): libfprint-image_device-DEBUG: 03:38:16.372: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 149s (process:4115): libfprint-image_device-DEBUG: 03:38:16.372: Deactivating image device 149s (process:4115): libfprint-image_device-DEBUG: 03:38:16.372: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 149s (process:4115): libfprint-image_device-DEBUG: 03:38:16.372: Image device deactivation completed 149s (process:4115): libfprint-image_device-DEBUG: 03:38:16.372: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 149s (process:4115): libfprint-device-DEBUG: 03:38:16.372: Device reported capture completion 149s (process:4115): libfprint-SSM-DEBUG: 03:38:16.372: [elanspi] ELANSPI_FPCAPT_NSTATES completed successfully 149s (process:4115): libfprint-device-DEBUG: 03:38:16.372: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 149s (process:4115): libfprint-device-DEBUG: 03:38:16.372: Updated temperature model after 5.84 seconds, ratio 0.27 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 149s (process:4115): libfprint-image_device-DEBUG: 03:38:16.372: Image device close completed 149s (process:4115): libfprint-device-DEBUG: 03:38:16.372: Device reported close completion 149s (process:4115): libfprint-device-DEBUG: 03:38:16.372: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 149s (process:4115): libfprint-device-DEBUG: 03:38:16.372: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 149s ** (umockdev-run:4111): DEBUG: 03:38:16.674: umockdev.vala:154: Removing test bed /tmp/umockdev.IMS612 149s (umockdev-run:4111): GLib-DEBUG: 03:38:16.686: unsetenv() is not thread-safe and should not be used after threads are created 149s Comparing PNGs /tmp/libfprint-umockdev-test-objalb_j/capture.png and /usr/share/installed-tests/libfprint-2/elanspi/capture.png 149s PASS: libfprint-2/driver-elanspi.test 149s Running test: libfprint-2/driver-upektc_img-tcs1s.test 149s ** (umockdev-run:4126): DEBUG: 03:38:16.802: umockdev.vala:127: Created udev test bed /tmp/umockdev.06HI22 149s ** (umockdev-run:4126): DEBUG: 03:38:16.802: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3/3-2 149s ** (umockdev-run:4126): DEBUG: 03:38:16.807: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3/3-2 (subsystem usb) 149s ** (umockdev-run:4126): DEBUG: 03:38:16.810: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.06HI22/dev/bus/usb/003/004 149s ** (umockdev-run:4126): DEBUG: 03:38:16.811: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3 149s ** (umockdev-run:4126): DEBUG: 03:38:16.814: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3 (subsystem usb) 149s ** (umockdev-run:4126): DEBUG: 03:38:16.818: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.06HI22/dev/bus/usb/003/001 149s ** (umockdev-run:4126): DEBUG: 03:38:16.818: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4 149s ** (umockdev-run:4126): DEBUG: 03:38:16.820: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4 (subsystem pci) 149s ** (umockdev-run:4126): DEBUG: 03:38:16.823: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:08.1 149s ** (umockdev-run:4126): DEBUG: 03:38:16.824: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:08.1 (subsystem pci) 149s (process:4130): libfprint-context-DEBUG: 03:38:16.918: Initializing FpContext (libfprint version 1.94.8+tod1) 149s (process:4130): libfprint-tod-DEBUG: 03:38:16.918: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 149s (process:4130): libfprint-context-DEBUG: 03:38:16.920: No driver found for USB device 1D6B:0002 149s (process:4130): libfprint-device-DEBUG: 03:38:16.921: Device reported probe completion 149s (process:4130): libfprint-device-DEBUG: 03:38:16.921: Completing action FPI_DEVICE_ACTION_PROBE in idle! 149s (process:4130): libfprint-device-DEBUG: 03:38:16.921: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 149s (process:4130): libfprint-image_device-DEBUG: 03:38:16.922: Image device open completed 149s (process:4130): libfprint-device-DEBUG: 03:38:16.922: Device reported open completion 149s (process:4130): libfprint-device-DEBUG: 03:38:16.922: Completing action FPI_DEVICE_ACTION_OPEN in idle! 149s (process:4130): libfprint-device-DEBUG: 03:38:16.922: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 149s (process:4130): libfprint-device-DEBUG: 03:38:16.922: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 149s (process:4130): libfprint-image_device-DEBUG: 03:38:16.922: Activating image device 149s (process:4130): libfprint-image_device-DEBUG: 03:38:16.922: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.922: [upektc_img] ACTIVATE_NUM_STATES entering state 0 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.923: [upektc_img] ACTIVATE_NUM_STATES entering state 1 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.925: [upektc_img] ACTIVATE_NUM_STATES entering state 2 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.926: [upektc_img] ACTIVATE_NUM_STATES entering state 3 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.927: [upektc_img] ACTIVATE_NUM_STATES entering state 4 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.927: [upektc_img] ACTIVATE_NUM_STATES entering state 5 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.928: [upektc_img] ACTIVATE_NUM_STATES entering state 6 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.929: [upektc_img] ACTIVATE_NUM_STATES entering state 7 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.930: [upektc_img] ACTIVATE_NUM_STATES entering state 8 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.930: [upektc_img] ACTIVATE_NUM_STATES entering state 9 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.931: [upektc_img] ACTIVATE_NUM_STATES entering state 10 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.932: [upektc_img] ACTIVATE_NUM_STATES entering state 11 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.932: Sensor type : TCS1x, width x height: 256 x 360 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.932: [upektc_img] ACTIVATE_NUM_STATES completed successfully 149s (process:4130): libfprint-image_device-DEBUG: 03:38:16.933: Image device activation completed 149s (process:4130): libfprint-image_device-DEBUG: 03:38:16.933: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 149s (process:4130): libfprint-image_device-DEBUG: 03:38:16.933: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 149s (process:4130): libfprint-device-DEBUG: 03:38:16.933: Device reported finger status change: FP_FINGER_STATUS_NEEDED 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.933: [upektc_img] CAPTURE_NUM_STATES entering state 0 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.933: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.934: request completed, len: 0000 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.934: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.934: request completed, len: 0040 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.934: 18th byte is 0c 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.934: [upektc_img] CAPTURE_NUM_STATES entering state 3 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.935: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.936: request completed, len: 0000 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.936: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.936: request completed, len: 0040 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.936: 18th byte is 13 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.936: [upektc_img] CAPTURE_NUM_STATES entering state 3 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.937: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.938: request completed, len: 0000 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.938: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.938: request completed, len: 0040 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.938: 18th byte is 00 149s (process:4130): libfprint-device-DEBUG: 03:38:16.938: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.938: [upektc_img] CAPTURE_NUM_STATES entering state 3 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.939: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.939: request completed, len: 0000 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.939: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.940: request completed, len: 0040 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.940: response_size is 2052, actual_length is 64 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.940: Waiting for rest of transfer 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.940: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.941: request completed, len: 07c4 149s (process:4130): libfprint-image_device-DEBUG: 03:38:16.941: Image device reported finger status: on 149s (process:4130): libfprint-image_device-DEBUG: 03:38:16.941: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.941: [upektc_img] CAPTURE_NUM_STATES entering state 5 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.941: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.942: request completed, len: 0040 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.942: response_size is 2052, actual_length is 64 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.942: Waiting for rest of transfer 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.942: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.943: request completed, len: 07c4 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.943: [upektc_img] CAPTURE_NUM_STATES entering state 5 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.944: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.944: request completed, len: 0040 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.944: response_size is 2052, actual_length is 64 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.944: Waiting for rest of transfer 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.944: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.945: request completed, len: 07c4 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.945: [upektc_img] CAPTURE_NUM_STATES entering state 5 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.946: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.946: request completed, len: 0040 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.946: response_size is 2052, actual_length is 64 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.946: Waiting for rest of transfer 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.946: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.947: request completed, len: 07c4 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.947: [upektc_img] CAPTURE_NUM_STATES entering state 5 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.948: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.949: request completed, len: 0040 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.949: response_size is 2052, actual_length is 64 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.949: Waiting for rest of transfer 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.949: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.949: request completed, len: 07c4 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.949: [upektc_img] CAPTURE_NUM_STATES entering state 5 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.950: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.951: request completed, len: 0040 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.951: response_size is 2052, actual_length is 64 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.951: Waiting for rest of transfer 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.951: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.952: request completed, len: 07c4 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.952: [upektc_img] CAPTURE_NUM_STATES entering state 5 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.953: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.953: request completed, len: 0040 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.953: response_size is 2052, actual_length is 64 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.953: Waiting for rest of transfer 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.953: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.954: request completed, len: 07c4 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.954: [upektc_img] CAPTURE_NUM_STATES entering state 5 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.955: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.955: request completed, len: 0040 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.955: response_size is 2052, actual_length is 64 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.955: Waiting for rest of transfer 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.955: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.956: request completed, len: 07c4 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.956: [upektc_img] CAPTURE_NUM_STATES entering state 5 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.957: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.957: request completed, len: 0040 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.957: response_size is 2052, actual_length is 64 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.957: Waiting for rest of transfer 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.957: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.958: request completed, len: 07c4 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.958: [upektc_img] CAPTURE_NUM_STATES entering state 5 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.959: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.959: request completed, len: 0040 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.959: response_size is 2052, actual_length is 64 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.959: Waiting for rest of transfer 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.959: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.960: request completed, len: 07c4 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.960: [upektc_img] CAPTURE_NUM_STATES entering state 5 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.961: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.961: request completed, len: 0040 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.961: response_size is 2052, actual_length is 64 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.961: Waiting for rest of transfer 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.961: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.962: request completed, len: 07c4 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.962: [upektc_img] CAPTURE_NUM_STATES entering state 5 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.963: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.963: request completed, len: 0040 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.963: response_size is 2052, actual_length is 64 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.963: Waiting for rest of transfer 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.963: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.964: request completed, len: 07c4 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.964: [upektc_img] CAPTURE_NUM_STATES entering state 5 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.965: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.965: request completed, len: 0040 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.965: response_size is 2052, actual_length is 64 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.965: Waiting for rest of transfer 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.965: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.966: request completed, len: 07c4 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.966: [upektc_img] CAPTURE_NUM_STATES entering state 5 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.967: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.967: request completed, len: 0040 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.967: response_size is 2052, actual_length is 64 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.967: Waiting for rest of transfer 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.967: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.968: request completed, len: 07c4 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.968: [upektc_img] CAPTURE_NUM_STATES entering state 5 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.969: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.969: request completed, len: 0040 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.969: response_size is 2052, actual_length is 64 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.970: Waiting for rest of transfer 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.970: [upektc_img] CAPTURE_NUM_STATES entering state 1 149s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.971: request completed, len: 07c4 149s (process:4130): libfprint-SSM-DEBUG: 03:38:16.971: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:4130): libfprint-SSM-DEBUG: 03:38:16.972: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.973: request completed, len: 0040 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.973: response_size is 2052, actual_length is 64 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.973: Waiting for rest of transfer 150s (process:4130): libfprint-SSM-DEBUG: 03:38:16.973: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.973: request completed, len: 07c4 150s (process:4130): libfprint-SSM-DEBUG: 03:38:16.973: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:4130): libfprint-SSM-DEBUG: 03:38:16.974: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.975: request completed, len: 0040 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.975: response_size is 2052, actual_length is 64 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.975: Waiting for rest of transfer 150s (process:4130): libfprint-SSM-DEBUG: 03:38:16.975: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.976: request completed, len: 07c4 150s (process:4130): libfprint-SSM-DEBUG: 03:38:16.976: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:4130): libfprint-SSM-DEBUG: 03:38:16.976: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.977: request completed, len: 0040 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.977: response_size is 2052, actual_length is 64 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.977: Waiting for rest of transfer 150s (process:4130): libfprint-SSM-DEBUG: 03:38:16.977: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.979: request completed, len: 07c4 150s (process:4130): libfprint-SSM-DEBUG: 03:38:16.979: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:4130): libfprint-SSM-DEBUG: 03:38:16.979: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.981: request completed, len: 0040 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.981: response_size is 2052, actual_length is 64 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.981: Waiting for rest of transfer 150s (process:4130): libfprint-SSM-DEBUG: 03:38:16.981: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.981: request completed, len: 07c4 150s (process:4130): libfprint-SSM-DEBUG: 03:38:16.981: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:4130): libfprint-SSM-DEBUG: 03:38:16.982: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.983: request completed, len: 0040 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.983: response_size is 2052, actual_length is 64 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.983: Waiting for rest of transfer 150s (process:4130): libfprint-SSM-DEBUG: 03:38:16.983: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.985: request completed, len: 07c4 150s (process:4130): libfprint-SSM-DEBUG: 03:38:16.985: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:4130): libfprint-SSM-DEBUG: 03:38:16.986: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.987: request completed, len: 0040 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.987: response_size is 2052, actual_length is 64 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.987: Waiting for rest of transfer 150s (process:4130): libfprint-SSM-DEBUG: 03:38:16.987: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.987: request completed, len: 07c4 150s (process:4130): libfprint-SSM-DEBUG: 03:38:16.987: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:4130): libfprint-SSM-DEBUG: 03:38:16.988: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.989: request completed, len: 0040 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.989: response_size is 2052, actual_length is 64 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.989: Waiting for rest of transfer 150s (process:4130): libfprint-SSM-DEBUG: 03:38:16.989: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.990: request completed, len: 07c4 150s (process:4130): libfprint-SSM-DEBUG: 03:38:16.990: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:4130): libfprint-SSM-DEBUG: 03:38:16.990: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.991: request completed, len: 0040 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.991: response_size is 2052, actual_length is 64 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.991: Waiting for rest of transfer 150s (process:4130): libfprint-SSM-DEBUG: 03:38:16.991: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.992: request completed, len: 07c4 150s (process:4130): libfprint-SSM-DEBUG: 03:38:16.992: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:4130): libfprint-SSM-DEBUG: 03:38:16.993: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.993: request completed, len: 0040 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.993: response_size is 2052, actual_length is 64 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.993: Waiting for rest of transfer 150s (process:4130): libfprint-SSM-DEBUG: 03:38:16.993: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.994: request completed, len: 07c4 150s (process:4130): libfprint-SSM-DEBUG: 03:38:16.994: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:4130): libfprint-SSM-DEBUG: 03:38:16.995: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.996: request completed, len: 0040 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.996: response_size is 2052, actual_length is 64 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.996: Waiting for rest of transfer 150s (process:4130): libfprint-SSM-DEBUG: 03:38:16.996: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.996: request completed, len: 07c4 150s (process:4130): libfprint-SSM-DEBUG: 03:38:16.996: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:4130): libfprint-SSM-DEBUG: 03:38:16.997: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.998: request completed, len: 0040 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.998: response_size is 814, actual_length is 64 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.998: Waiting for rest of transfer 150s (process:4130): libfprint-SSM-DEBUG: 03:38:16.998: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.998: request completed, len: 02ee 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:16.999: Image size is 51840 150s (process:4130): libfprint-image_device-DEBUG: 03:38:16.999: Image device captured an image 150s (process:4130): libfprint-image_device-DEBUG: 03:38:16.999: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 150s (process:4130): libfprint-device-DEBUG: 03:38:17.000: Device reported finger status change: FP_FINGER_STATUS_PRESENT 150s (process:4130): libfprint-device-DEBUG: 03:38:17.000: Device reported finger status change: FP_FINGER_STATUS_NONE 150s (process:4130): libfprint-image_device-DEBUG: 03:38:17.000: Image device reported finger status: off 150s (process:4130): libfprint-image_device-DEBUG: 03:38:17.000: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 150s (process:4130): libfprint-image_device-DEBUG: 03:38:17.000: Deactivating image device 150s (process:4130): libfprint-image_device-DEBUG: 03:38:17.000: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 150s (process:4130): libfprint-SSM-DEBUG: 03:38:17.000: [upektc_img] CAPTURE_NUM_STATES completed successfully 150s (process:4130): libfprint-SSM-DEBUG: 03:38:17.000: [upektc_img] DEACTIVATE_NUM_STATES entering state 0 150s (process:4130): libfprint-SSM-DEBUG: 03:38:17.001: [upektc_img] DEACTIVATE_NUM_STATES entering state 1 150s (process:4130): libfprint-SSM-DEBUG: 03:38:17.001: [upektc_img] DEACTIVATE_NUM_STATES completed successfully 150s (process:4130): libfprint-upektc_img-DEBUG: 03:38:17.001: Deactivate completed 150s (process:4130): libfprint-image_device-DEBUG: 03:38:17.001: Image device deactivation completed 150s (process:4130): libfprint-image_device-DEBUG: 03:38:17.001: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 150s (process:4130): libfprint-image-DEBUG: 03:38:17.021: Minutiae scan completed in 0.021719 secs 150s (process:4130): libfprint-device-DEBUG: 03:38:17.021: Device reported capture completion 150s (process:4130): libfprint-device-DEBUG: 03:38:17.021: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 150s (process:4130): libfprint-device-DEBUG: 03:38:17.021: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 150s (process:4130): libfprint-image_device-DEBUG: 03:38:17.021: Image device close completed 150s (process:4130): libfprint-device-DEBUG: 03:38:17.021: Device reported close completion 150s (process:4130): libfprint-device-DEBUG: 03:38:17.022: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 150s (process:4130): libfprint-device-DEBUG: 03:38:17.022: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 150s ** (umockdev-run:4126): DEBUG: 03:38:17.139: umockdev.vala:154: Removing test bed /tmp/umockdev.06HI22 150s (umockdev-run:4126): GLib-DEBUG: 03:38:17.147: unsetenv() is not thread-safe and should not be used after threads are created 150s Comparing PNGs /tmp/libfprint-umockdev-test-g2v2m7jd/capture.png and /usr/share/installed-tests/libfprint-2/upektc_img-tcs1s/capture.png 150s PASS: libfprint-2/driver-upektc_img-tcs1s.test 150s Running test: libfprint-2/driver-egis0570.test 150s ** (umockdev-run:4139): DEBUG: 03:38:17.212: umockdev.vala:127: Created udev test bed /tmp/umockdev.W61212 150s ** (umockdev-run:4139): DEBUG: 03:38:17.212: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 150s ** (umockdev-run:4139): DEBUG: 03:38:17.214: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 150s ** (umockdev-run:4139): DEBUG: 03:38:17.218: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.W61212/dev/bus/usb/001/005 150s ** (umockdev-run:4139): DEBUG: 03:38:17.218: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 150s ** (umockdev-run:4139): DEBUG: 03:38:17.219: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 150s ** (umockdev-run:4139): DEBUG: 03:38:17.223: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.W61212/dev/bus/usb/001/001 150s ** (umockdev-run:4139): DEBUG: 03:38:17.223: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 150s ** (umockdev-run:4139): DEBUG: 03:38:17.223: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 150s (process:4143): libfprint-context-DEBUG: 03:38:17.313: Initializing FpContext (libfprint version 1.94.8+tod1) 150s (process:4143): libfprint-tod-DEBUG: 03:38:17.313: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 150s (process:4143): libfprint-context-DEBUG: 03:38:17.315: No driver found for USB device 1D6B:0002 150s (process:4143): libfprint-device-DEBUG: 03:38:17.316: Device reported probe completion 150s (process:4143): libfprint-device-DEBUG: 03:38:17.316: Completing action FPI_DEVICE_ACTION_PROBE in idle! 150s (process:4143): libfprint-device-DEBUG: 03:38:17.316: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.318: Image device open completed 150s (process:4143): libfprint-device-DEBUG: 03:38:17.318: Device reported open completion 150s (process:4143): libfprint-device-DEBUG: 03:38:17.318: Completing action FPI_DEVICE_ACTION_OPEN in idle! 150s (process:4143): libfprint-device-DEBUG: 03:38:17.318: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 150s (process:4143): libfprint-device-DEBUG: 03:38:17.318: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.318: Activating image device 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.318: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.318: [egis0570] SM_STATES_NUM entering state 0 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.318: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.318: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.318: Image device activation completed 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.318: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.318: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 150s (process:4143): libfprint-device-DEBUG: 03:38:17.318: Device reported finger status change: FP_FINGER_STATUS_NEEDED 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.319: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.319: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.320: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.320: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.321: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.321: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.322: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.323: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.323: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.324: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.325: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.325: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.326: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.326: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.327: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.327: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.328: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.328: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.330: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.330: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.331: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.334: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.335: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.336: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.336: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.337: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.338: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.338: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.339: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.339: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.340: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.340: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.341: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.341: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.342: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.342: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.343: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.344: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.344: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.345: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.346: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.346: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.347: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.347: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.348: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.348: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.349: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.349: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.349: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.349: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.349: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.350: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.350: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.351: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.351: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.352: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.353: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.353: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.353: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.353: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.353: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.353: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.353: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.353: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.353: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.353: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.353: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.354: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.354: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.355: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.355: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.356: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.356: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.357: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.357: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.358: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.358: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.358: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.358: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.358: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.358: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.358: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.358: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.358: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.358: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.359: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.359: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.360: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.361: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.362: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.362: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.362: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.363: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.363: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.363: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.363: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.363: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.363: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.363: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.363: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.363: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.364: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.364: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.367: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.367: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.370: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.370: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.371: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.371: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.372: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.372: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.372: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.372: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.372: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.372: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.372: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.372: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.372: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.374: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.375: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.376: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.376: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.377: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.377: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.379: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.379: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.379: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.379: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.379: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.379: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.379: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.379: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.379: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.379: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.379: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.380: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.380: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.381: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.381: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.382: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.383: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.383: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.383: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.384: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.384: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.384: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.384: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.384: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.384: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.384: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.384: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.384: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.385: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.385: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.386: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.386: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.388: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.388: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.389: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.390: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.390: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.390: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.390: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.390: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.391: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.391: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.391: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.391: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.391: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.391: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.391: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.392: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.393: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.393: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.394: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.395: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.395: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.396: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.396: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.396: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.396: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.396: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.396: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.396: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.396: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.396: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.397: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.398: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.399: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.399: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.400: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.401: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.401: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.401: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.402: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.402: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.402: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.402: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.402: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.402: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.402: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.402: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.402: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.403: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.403: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.404: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.405: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.406: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.407: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.407: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.408: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.409: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.409: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.409: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.409: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.410: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.410: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.410: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.410: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.410: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.410: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.412: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.413: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.413: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.414: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.414: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.415: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.415: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.416: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.416: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.416: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.416: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.416: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.416: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.416: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.416: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.416: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.416: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.417: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.418: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.418: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-device-DEBUG: 03:38:17.418: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.419: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.419: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.420: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.420: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.420: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.420: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.420: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.420: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.420: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.420: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.420: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.420: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.420: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.421: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.421: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.422: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.422: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.423: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.423: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.424: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.424: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.425: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.425: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.425: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.425: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.425: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.425: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.425: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.425: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.425: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.426: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.426: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.427: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.427: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.428: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.429: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.430: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.430: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.430: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.430: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.430: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.430: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.430: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.430: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.430: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.430: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.430: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.431: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.431: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.432: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.432: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.433: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.433: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.434: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.434: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.435: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.435: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.435: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.435: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.435: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.435: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.435: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.435: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.435: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.435: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.436: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.437: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.437: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.438: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.438: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.439: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.439: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.439: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.440: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.440: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.440: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.440: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.440: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.440: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.440: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.440: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.440: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.440: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.441: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.441: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.442: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.443: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.443: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.443: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.444: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.444: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.444: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.444: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.444: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.444: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.444: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.444: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.444: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.445: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.445: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.446: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.446: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.447: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.447: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.448: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.448: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.449: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.449: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.449: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.449: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.449: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.449: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.449: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.449: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.449: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.449: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.449: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.450: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.451: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.451: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.452: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.453: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.453: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.454: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.454: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.454: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.454: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.454: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.454: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.454: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.454: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.454: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.455: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.455: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.456: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.456: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.457: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.457: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.458: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.458: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.459: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.459: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.459: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.459: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.459: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.459: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.459: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.459: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.459: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.459: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.460: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.460: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.461: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.461: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.462: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.462: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.462: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.463: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.463: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.463: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.463: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.463: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.463: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.463: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.463: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.463: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.464: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.464: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.465: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.465: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.466: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.466: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.467: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.467: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.468: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.468: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.468: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.468: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.468: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.468: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.468: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.468: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.468: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.468: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.468: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.469: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.470: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.470: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.471: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.471: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.471: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.473: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.473: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.473: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.473: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.473: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.473: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.473: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.473: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.473: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.473: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.474: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.474: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.475: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.475: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.476: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.476: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.477: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.477: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.477: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.477: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.477: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.477: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.477: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.477: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.477: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.477: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.478: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.478: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.479: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.479: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.480: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.480: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.481: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.481: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.481: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.481: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.481: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.481: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.481: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.481: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.481: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.481: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.481: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.482: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.482: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.483: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.483: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.484: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.484: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.485: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.485: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.486: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.486: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.486: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.486: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.486: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.486: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.486: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.486: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.486: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.486: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.487: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.488: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.488: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.489: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.489: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.490: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.490: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.490: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.490: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.490: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.490: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.490: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.490: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.490: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.490: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.490: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.491: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.491: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.493: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.493: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.494: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.494: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.495: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.495: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.496: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.496: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.496: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.496: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.496: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.496: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.496: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.496: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.496: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.496: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.497: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.498: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.498: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.499: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.500: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.500: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.500: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.501: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.501: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.501: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.501: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.501: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.501: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.501: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.501: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.501: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.501: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.502: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.503: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.503: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.504: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.504: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.505: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.505: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.505: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.505: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.505: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.505: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.505: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.505: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.505: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.505: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.505: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.506: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.506: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.507: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.507: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.508: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.509: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.509: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.509: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.510: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.510: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.510: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.510: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.510: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.510: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.510: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.510: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.510: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.511: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.511: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.513: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.513: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.514: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.515: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.515: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.515: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.516: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.516: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.517: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.517: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.517: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.517: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.517: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.517: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.517: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.517: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.517: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.518: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.518: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.519: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.519: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.521: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.521: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.521: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.521: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.521: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.521: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.521: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.521: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.521: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.521: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.521: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.522: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.522: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.523: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.523: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.524: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.525: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.525: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.525: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.526: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.526: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.526: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.526: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.526: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.526: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.526: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.526: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.526: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.527: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.527: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.528: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.528: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.529: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.529: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.530: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.530: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.531: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.531: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.531: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.531: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.531: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.531: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.531: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.531: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.531: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.531: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.532: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.532: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.533: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.533: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.534: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.534: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.534: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.535: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.535: Finger status (picture number, mean) : 1 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.535: Finger status (picture number, mean) : 2 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.535: Finger status (picture number, mean) : 3 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.535: Finger status (picture number, mean) : 4 , 0 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.535: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.535: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.535: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.535: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.536: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.536: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.537: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.537: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.538: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.538: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.539: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.539: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.540: Finger status (picture number, mean) : 0 , 0 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.540: Finger status (picture number, mean) : 1 , 1 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.540: Finger status (picture number, mean) : 2 , 2 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.540: Finger status (picture number, mean) : 3 , 3 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.540: Finger status (picture number, mean) : 4 , 6 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.540: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.540: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.540: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.540: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.540: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.541: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.541: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.542: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.542: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.543: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.544: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.544: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.544: Finger status (picture number, mean) : 0 , 11 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.544: Finger status (picture number, mean) : 1 , 16 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.544: Finger status (picture number, mean) : 2 , 23 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.544: Finger status (picture number, mean) : 3 , 28 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.544: Finger status (picture number, mean) : 4 , 32 150s (process:4143): libfprint-device-DEBUG: 03:38:17.544: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.544: Image device reported finger status: on 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.544: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 150s (process:4143): libfprint-device-DEBUG: 03:38:17.544: Device reported finger status change: FP_FINGER_STATUS_NEEDED 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.544: Image device reported finger status: off 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.544: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.544: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.544: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.545: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.545: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.546: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.546: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.547: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.547: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.548: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.548: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.549: Finger status (picture number, mean) : 0 , 38 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.549: Finger status (picture number, mean) : 1 , 43 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.549: Finger status (picture number, mean) : 2 , 48 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.549: Finger status (picture number, mean) : 3 , 54 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.549: Finger status (picture number, mean) : 4 , 58 150s (process:4143): libfprint-device-DEBUG: 03:38:17.549: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.549: Image device reported finger status: on 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.549: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.549: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.549: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.549: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.550: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.551: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.551: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.552: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.552: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.553: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.553: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.553: Finger status (picture number, mean) : 0 , 62 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.553: Finger status (picture number, mean) : 1 , 68 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.553: Finger status (picture number, mean) : 2 , 71 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.553: Finger status (picture number, mean) : 3 , 73 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.553: Finger status (picture number, mean) : 4 , 77 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.553: Image device reported finger status: on 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.553: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.553: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.553: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.554: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.554: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.555: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.555: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.558: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.558: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.559: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.559: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.560: Finger status (picture number, mean) : 0 , 79 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.560: Finger status (picture number, mean) : 1 , 79 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.560: Finger status (picture number, mean) : 2 , 82 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.560: Finger status (picture number, mean) : 3 , 84 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.560: Finger status (picture number, mean) : 4 , 85 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.560: Image device reported finger status: on 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.560: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.560: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.560: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.560: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.561: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.561: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.562: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.562: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.563: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.564: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.564: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.564: Finger status (picture number, mean) : 0 , 88 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.564: Finger status (picture number, mean) : 1 , 89 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.564: Finger status (picture number, mean) : 2 , 90 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.564: Finger status (picture number, mean) : 3 , 92 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.564: Finger status (picture number, mean) : 4 , 92 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.564: Image device reported finger status: on 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.564: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.564: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.564: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.565: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.565: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.566: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.566: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.567: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.567: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.568: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.568: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.569: Finger status (picture number, mean) : 0 , 93 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.569: Finger status (picture number, mean) : 1 , 94 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.569: Finger status (picture number, mean) : 2 , 95 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.569: Finger status (picture number, mean) : 3 , 96 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.569: Finger status (picture number, mean) : 4 , 97 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.569: Image device reported finger status: on 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.569: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.569: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.569: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.569: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.570: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.571: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.571: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.572: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.574: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.575: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.575: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.576: Finger status (picture number, mean) : 0 , 97 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.576: Finger status (picture number, mean) : 1 , 95 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.576: Finger status (picture number, mean) : 2 , 95 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.576: Finger status (picture number, mean) : 3 , 96 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.576: Finger status (picture number, mean) : 4 , 97 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.576: Image device reported finger status: on 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.576: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.576: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.576: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.576: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.576: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.577: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.578: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.578: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.579: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.579: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.579: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.580: Finger status (picture number, mean) : 0 , 96 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.580: Finger status (picture number, mean) : 1 , 97 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.580: Finger status (picture number, mean) : 2 , 98 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.580: Finger status (picture number, mean) : 3 , 98 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.580: Finger status (picture number, mean) : 4 , 98 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.580: Image device reported finger status: on 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.580: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.580: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.580: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.581: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.581: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.582: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.582: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.583: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.584: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.584: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.584: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.585: Finger status (picture number, mean) : 0 , 98 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.585: Finger status (picture number, mean) : 1 , 99 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.585: Finger status (picture number, mean) : 2 , 100 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.585: Finger status (picture number, mean) : 3 , 99 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.585: Finger status (picture number, mean) : 4 , 97 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.585: Image device reported finger status: on 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.585: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.585: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.585: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.586: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.586: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.587: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.587: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.588: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.588: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.589: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.589: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.589: Finger status (picture number, mean) : 0 , 98 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.589: Finger status (picture number, mean) : 1 , 98 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.589: Finger status (picture number, mean) : 2 , 98 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.589: Finger status (picture number, mean) : 3 , 95 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.589: Finger status (picture number, mean) : 4 , 91 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.589: Image device reported finger status: on 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.589: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.589: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.589: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.590: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.591: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.592: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.592: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.593: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.593: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.594: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.594: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.594: Finger status (picture number, mean) : 0 , 88 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.595: Finger status (picture number, mean) : 1 , 88 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.595: Finger status (picture number, mean) : 2 , 88 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.595: Finger status (picture number, mean) : 3 , 87 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.595: Finger status (picture number, mean) : 4 , 89 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.595: Image device reported finger status: on 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.595: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.595: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.595: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.595: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.595: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.598: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.598: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.599: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.599: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.601: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.601: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.602: Finger status (picture number, mean) : 0 , 88 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.602: Finger status (picture number, mean) : 1 , 89 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.602: Finger status (picture number, mean) : 2 , 90 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.602: Finger status (picture number, mean) : 3 , 91 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.602: Finger status (picture number, mean) : 4 , 89 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.602: Image device reported finger status: on 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.602: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.602: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.602: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.603: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.603: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.604: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.604: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.605: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.605: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.606: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.606: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.606: Finger status (picture number, mean) : 0 , 90 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.606: Finger status (picture number, mean) : 1 , 89 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.607: Finger status (picture number, mean) : 2 , 85 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.607: Finger status (picture number, mean) : 3 , 75 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.607: Finger status (picture number, mean) : 4 , 46 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.607: Image device reported finger status: on 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.607: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.607: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.607: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.607: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.607: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.608: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.608: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.609: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.610: [egis0570] SM_STATES_NUM entering state 2 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.611: [egis0570] SM_STATES_NUM entering state 3 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.611: [egis0570] SM_STATES_NUM entering state 4 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.611: Finger status (picture number, mean) : 0 , 17 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.611: Finger status (picture number, mean) : 1 , 14 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.611: Finger status (picture number, mean) : 2 , 15 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.611: Finger status (picture number, mean) : 3 , 15 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.611: Finger status (picture number, mean) : 4 , 15 150s (process:4143): libfprint-assembling-DEBUG: 03:38:17.667: calc delta completed in 0.056223 secs 150s (process:4143): libfprint-assembling-DEBUG: 03:38:17.724: calc delta completed in 0.056166 secs 150s (process:4143): libfprint-assembling-DEBUG: 03:38:17.724: errors: 10243 rev: 29954 150s (process:4143): libfprint-assembling-DEBUG: 03:38:17.780: calc delta completed in 0.056085 secs 150s (process:4143): libfprint-assembling-DEBUG: 03:38:17.780: height is 292 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.782: Image device captured an image 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.782: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 150s (process:4143): libfprint-device-DEBUG: 03:38:17.782: Device reported finger status change: FP_FINGER_STATUS_PRESENT 150s (process:4143): libfprint-device-DEBUG: 03:38:17.784: Device reported finger status change: FP_FINGER_STATUS_NONE 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.784: Image device reported finger status: off 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.784: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.784: Deactivating image device 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.784: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.784: [egis0570] SM_STATES_NUM entering state 5 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.784: [egis0570] SM_STATES_NUM entering state 1 150s (process:4143): libfprint-egis0570-DEBUG: 03:38:17.784: deactivating, marking completed 150s (process:4143): libfprint-SSM-DEBUG: 03:38:17.784: [egis0570] SM_STATES_NUM completed successfully 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.784: Image device deactivation completed 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.784: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 150s (process:4143): libfprint-image-DEBUG: 03:38:17.833: Minutiae scan completed in 0.050545 secs 150s (process:4143): libfprint-device-DEBUG: 03:38:17.833: Device reported capture completion 150s (process:4143): libfprint-device-DEBUG: 03:38:17.833: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 150s (process:4143): libfprint-device-DEBUG: 03:38:17.833: Updated temperature model after 0.42 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 150s (process:4143): libfprint-image_device-DEBUG: 03:38:17.834: Image device close completed 150s (process:4143): libfprint-device-DEBUG: 03:38:17.834: Device reported close completion 150s (process:4143): libfprint-device-DEBUG: 03:38:17.834: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 150s (process:4143): libfprint-device-DEBUG: 03:38:17.834: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 151s ** (umockdev-run:4139): DEBUG: 03:38:18.170: umockdev.vala:154: Removing test bed /tmp/umockdev.W61212 151s (umockdev-run:4139): GLib-DEBUG: 03:38:18.176: unsetenv() is not thread-safe and should not be used after threads are created 151s Comparing PNGs /tmp/libfprint-umockdev-test-_fftdsn2/capture.png and /usr/share/installed-tests/libfprint-2/egis0570/capture.png 151s PASS: libfprint-2/driver-egis0570.test 151s Running test: libfprint-2/fp-context.test 151s TAP version 14 151s # random seed: R02Sc90745d25e0d717eb2938cb81741f4e3 151s 1..9 151s # Start of context tests 151s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 151s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 151s ok 1 /context/new 151s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 151s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 151s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 151s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 151s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 151s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 151s ok 2 /context/no-devices 151s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 151s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 151s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 151s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 151s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 151s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 151s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 151s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-CCJ312/virtual_image.socket 151s # libfprint-context-DEBUG: created 151s # libfprint-device-DEBUG: Device reported probe completion 151s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 151s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 151s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 151s ok 3 /context/has-virtual-device 151s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 151s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 151s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 151s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 151s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 151s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 151s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 151s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-GP7612/virtual_image.socket 151s # libfprint-context-DEBUG: created 151s # libfprint-device-DEBUG: Device reported probe completion 151s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 151s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 151s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 151s ok 4 /context/enumerates-new-devices 151s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 151s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 151s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 151s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 151s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 151s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 151s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 151s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-QR6612/virtual_image.socket 151s # libfprint-context-DEBUG: created 151s # libfprint-device-DEBUG: Device reported probe completion 151s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 151s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 151s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 151s ok 5 /context/remove-device-closed 151s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 151s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 151s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 151s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 151s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 151s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 151s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 151s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-R81612/virtual_image.socket 151s # libfprint-context-DEBUG: created 151s # libfprint-device-DEBUG: Device reported probe completion 151s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 151s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 151s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:4150): libfprint-virtual_image-DEBUG: 03:38:18.273: 98081445: ../libfprint/drivers/virtual-image.c:216 151s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:4150): libfprint-virtual_device_connection-DEBUG: 03:38:18.273: 98081568: ../libfprint/drivers/virtual-device-listener.c:153 151s # libfprint-image_device-DEBUG: Image device open completed 151s # libfprint-device-DEBUG: Device reported open completion 151s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 151s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 151s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:4150): libfprint-virtual_image-DEBUG: 03:38:18.374: 98182180: ../libfprint/drivers/virtual-image.c:244 151s # libfprint-image_device-DEBUG: Image device close completed 151s # libfprint-device-DEBUG: Device reported close completion 151s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 151s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 151s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 151s ok 6 /context/remove-device-closing 151s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 151s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 151s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 151s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 151s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 151s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 151s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 151s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-ZBA812/virtual_image.socket 151s # libfprint-context-DEBUG: created 151s # libfprint-device-DEBUG: Device reported probe completion 151s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 151s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 151s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:4150): libfprint-virtual_image-DEBUG: 03:38:18.480: 98287893: ../libfprint/drivers/virtual-image.c:216 151s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:4150): libfprint-virtual_device_connection-DEBUG: 03:38:18.480: 98287930: ../libfprint/drivers/virtual-device-listener.c:153 151s # libfprint-image_device-DEBUG: Image device open completed 151s # libfprint-device-DEBUG: Device reported open completion 151s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 151s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 151s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:4150): libfprint-virtual_image-DEBUG: 03:38:18.580: 98388429: ../libfprint/drivers/virtual-image.c:244 151s # libfprint-image_device-DEBUG: Image device close completed 151s # libfprint-device-DEBUG: Device reported close completion 151s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 151s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 151s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 151s ok 7 /context/remove-device-open 151s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 151s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 151s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 151s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 151s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 151s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 151s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 151s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-FNGF22/virtual_image.socket 151s # libfprint-context-DEBUG: created 151s # libfprint-device-DEBUG: Device reported probe completion 151s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 151s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 151s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:4150): libfprint-virtual_image-DEBUG: 03:38:18.686: 98494088: ../libfprint/drivers/virtual-image.c:216 151s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:4150): libfprint-virtual_device_connection-DEBUG: 03:38:18.686: 98494124: ../libfprint/drivers/virtual-device-listener.c:153 151s # libfprint-image_device-DEBUG: Image device open completed 151s # libfprint-device-DEBUG: Device reported open completion 151s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 151s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 151s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:4150): libfprint-virtual_image-DEBUG: 03:38:18.787: 98594617: ../libfprint/drivers/virtual-image.c:244 151s # libfprint-image_device-DEBUG: Image device close completed 151s # libfprint-device-DEBUG: Device reported close completion 151s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 151s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 151s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 151s ok 8 /context/remove-device-opening 151s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 151s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 151s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 151s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 151s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 151s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 151s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 151s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-FUPH22/virtual_image.socket 151s # libfprint-context-DEBUG: created 151s # libfprint-device-DEBUG: Device reported probe completion 151s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 151s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 151s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:4150): libfprint-virtual_image-DEBUG: 03:38:18.892: 98699978: ../libfprint/drivers/virtual-image.c:216 151s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:4150): libfprint-virtual_device_connection-DEBUG: 03:38:18.892: 98700030: ../libfprint/drivers/virtual-device-listener.c:153 152s # libfprint-image_device-DEBUG: Image device open completed 152s # libfprint-device-DEBUG: Device reported open completion 152s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 152s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 152s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 152s # libfprint-image_device-DEBUG: Activating image device 152s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 152s # libfprint-image_device-DEBUG: Image device activation completed 152s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 152s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 152s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s # libfprint-image_device-DEBUG: Deactivating image device 152s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 152s # libfprint-image_device-DEBUG: Image device deactivation completed 152s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 152s # libfprint-device-DEBUG: Device reported generic error (The driver encountered a protocol error with the device.) during action; action was: FPI_DEVICE_ACTION_ENROLL 152s # libfprint-device-DEBUG: Device reported enroll completion 152s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE 152s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 152s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 152s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:4150): libfprint-virtual_image-DEBUG: 03:38:18.993: 98801011: ../libfprint/drivers/virtual-image.c:244 152s # libfprint-image_device-DEBUG: Image device close completed 152s # libfprint-device-DEBUG: Device reported close completion 152s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 152s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 152s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 152s ok 9 /context/remove-device-active 152s # End of context tests 152s PASS: libfprint-2/fp-context.test 152s Running test: libfprint-2/driver-aes3500.test 152s ** (umockdev-run:4174): DEBUG: 03:38:19.130: umockdev.vala:127: Created udev test bed /tmp/umockdev.FLL012 152s ** (umockdev-run:4174): DEBUG: 03:38:19.130: 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 152s ** (umockdev-run:4174): DEBUG: 03:38:19.133: 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) 152s ** (umockdev-run:4174): DEBUG: 03:38:19.136: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.FLL012/dev/bus/usb/003/004 152s ** (umockdev-run:4174): DEBUG: 03:38:19.136: 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 152s ** (umockdev-run:4174): DEBUG: 03:38:19.138: 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) 152s ** (umockdev-run:4174): DEBUG: 03:38:19.141: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.FLL012/dev/bus/usb/003/003 152s ** (umockdev-run:4174): DEBUG: 03:38:19.141: 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 152s ** (umockdev-run:4174): DEBUG: 03:38:19.143: 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) 152s ** (umockdev-run:4174): DEBUG: 03:38:19.146: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.FLL012/dev/bus/usb/003/002 152s ** (umockdev-run:4174): DEBUG: 03:38:19.146: 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 152s ** (umockdev-run:4174): DEBUG: 03:38:19.148: 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) 152s ** (umockdev-run:4174): DEBUG: 03:38:19.151: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.FLL012/dev/bus/usb/003/001 152s ** (umockdev-run:4174): DEBUG: 03:38:19.151: 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 152s ** (umockdev-run:4174): DEBUG: 03:38:19.153: 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) 152s ** (umockdev-run:4174): DEBUG: 03:38:19.155: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0 152s ** (umockdev-run:4174): DEBUG: 03:38:19.156: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0 (subsystem pci) 152s ** (umockdev-run:4174): DEBUG: 03:38:19.159: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0 152s ** (umockdev-run:4174): DEBUG: 03:38:19.159: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0 (subsystem pci) 152s ** (umockdev-run:4174): DEBUG: 03:38:19.162: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.0 152s ** (umockdev-run:4174): DEBUG: 03:38:19.162: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.0 (subsystem pci) 152s (umockdev-run:4174): GLib-GIO-DEBUG: 03:38:19.165: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 152s (process:4178): libfprint-context-DEBUG: 03:38:19.249: Initializing FpContext (libfprint version 1.94.8+tod1) 152s (process:4178): libfprint-tod-DEBUG: 03:38:19.249: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 152s (process:4178): libfprint-context-DEBUG: 03:38:19.253: No driver found for USB device 2230:0006 152s (process:4178): libfprint-context-DEBUG: 03:38:19.253: No driver found for USB device 2230:0006 152s (process:4178): libfprint-context-DEBUG: 03:38:19.253: No driver found for USB device 1D6B:0002 152s (process:4178): libfprint-device-DEBUG: 03:38:19.254: Device reported probe completion 152s (process:4178): libfprint-device-DEBUG: 03:38:19.254: Completing action FPI_DEVICE_ACTION_PROBE in idle! 152s (process:4178): libfprint-device-DEBUG: 03:38:19.254: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 152s (process:4178): libfprint-image_device-DEBUG: 03:38:19.256: Image device open completed 152s (process:4178): libfprint-device-DEBUG: 03:38:19.256: Device reported open completion 152s (process:4178): libfprint-device-DEBUG: 03:38:19.256: Completing action FPI_DEVICE_ACTION_OPEN in idle! 152s (process:4178): libfprint-device-DEBUG: 03:38:19.256: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 152s (process:4178): libfprint-device-DEBUG: 03:38:19.256: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 152s (process:4178): libfprint-image_device-DEBUG: 03:38:19.258: Activating image device 152s (process:4178): libfprint-image_device-DEBUG: 03:38:19.258: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 152s (process:4178): libfprint-aeslib-DEBUG: 03:38:19.259: write 50 regs 152s (process:4178): libfprint-aeslib-DEBUG: 03:38:19.266: all registers written 152s (process:4178): libfprint-image_device-DEBUG: 03:38:19.266: Image device activation completed 152s (process:4178): libfprint-image_device-DEBUG: 03:38:19.266: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 152s (process:4178): libfprint-image_device-DEBUG: 03:38:19.266: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 152s (process:4178): libfprint-aeslib-DEBUG: 03:38:19.266: write 6 regs 152s (process:4178): libfprint-device-DEBUG: 03:38:19.267: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:4178): libfprint-aeslib-DEBUG: 03:38:19.268: all registers written 152s (process:4178): libfprint-device-DEBUG: 03:38:19.269: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 152s (process:4178): libfprint-image_device-DEBUG: 03:38:19.269: Image device reported finger status: on 152s (process:4178): libfprint-image_device-DEBUG: 03:38:19.269: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 152s (process:4178): libfprint-aes3k-DEBUG: 03:38:19.269: frame header byte e0 152s (process:4178): libfprint-aes3k-DEBUG: 03:38:19.269: frame header byte e1 152s (process:4178): libfprint-aes3k-DEBUG: 03:38:19.269: frame header byte e2 152s (process:4178): libfprint-aes3k-DEBUG: 03:38:19.269: frame header byte e3 152s (process:4178): libfprint-aes3k-DEBUG: 03:38:19.270: frame header byte e4 152s (process:4178): libfprint-aes3k-DEBUG: 03:38:19.270: frame header byte e5 152s (process:4178): libfprint-aes3k-DEBUG: 03:38:19.270: frame header byte e6 152s (process:4178): libfprint-aes3k-DEBUG: 03:38:19.270: frame header byte e7 152s (process:4178): libfprint-image_device-DEBUG: 03:38:19.270: Image device captured an image 152s (process:4178): libfprint-image_device-DEBUG: 03:38:19.272: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 152s (process:4178): libfprint-device-DEBUG: 03:38:19.272: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:4178): libfprint-device-DEBUG: 03:38:19.272: Device reported finger status change: FP_FINGER_STATUS_NONE 152s (process:4178): libfprint-image_device-DEBUG: 03:38:19.272: Image device reported finger status: off 152s (process:4178): libfprint-image_device-DEBUG: 03:38:19.272: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 152s (process:4178): libfprint-image_device-DEBUG: 03:38:19.272: Deactivating image device 152s (process:4178): libfprint-image_device-DEBUG: 03:38:19.272: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 152s (process:4178): libfprint-image_device-DEBUG: 03:38:19.272: Image device deactivation completed 152s (process:4178): libfprint-image_device-DEBUG: 03:38:19.272: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 152s (process:4178): libfprint-image-DEBUG: 03:38:19.292: Minutiae scan completed in 0.021712 secs 152s (process:4178): libfprint-device-DEBUG: 03:38:19.292: Device reported capture completion 152s (process:4178): libfprint-device-DEBUG: 03:38:19.292: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 152s (process:4178): libfprint-device-DEBUG: 03:38:19.292: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 152s (process:4178): libfprint-image_device-DEBUG: 03:38:19.293: Image device close completed 152s (process:4178): libfprint-device-DEBUG: 03:38:19.293: Device reported close completion 152s (process:4178): libfprint-device-DEBUG: 03:38:19.293: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 152s (process:4178): libfprint-device-DEBUG: 03:38:19.293: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 152s ** (umockdev-run:4174): DEBUG: 03:38:19.427: umockdev.vala:154: Removing test bed /tmp/umockdev.FLL012 152s (umockdev-run:4174): GLib-DEBUG: 03:38:19.441: unsetenv() is not thread-safe and should not be used after threads are created 152s Comparing PNGs /tmp/libfprint-umockdev-test-apq698tz/capture.png and /usr/share/installed-tests/libfprint-2/aes3500/capture.png 152s PASS: libfprint-2/driver-aes3500.test 152s Running test: libfprint-2/driver-upektc_img.test 152s ** (umockdev-run:4187): DEBUG: 03:38:19.510: umockdev.vala:127: Created udev test bed /tmp/umockdev.KQY812 152s ** (umockdev-run:4187): DEBUG: 03:38:19.510: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3 152s ** (umockdev-run:4187): DEBUG: 03:38:19.511: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3 (subsystem usb) 152s ** (umockdev-run:4187): DEBUG: 03:38:19.515: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.KQY812/dev/bus/usb/001/003 152s ** (umockdev-run:4187): DEBUG: 03:38:19.515: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1/1-1 152s ** (umockdev-run:4187): DEBUG: 03:38:19.516: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1a.0/usb1/1-1 (subsystem usb) 152s ** (umockdev-run:4187): DEBUG: 03:38:19.519: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.KQY812/dev/bus/usb/001/002 152s ** (umockdev-run:4187): DEBUG: 03:38:19.519: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1 152s ** (umockdev-run:4187): DEBUG: 03:38:19.520: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1a.0/usb1 (subsystem usb) 152s ** (umockdev-run:4187): DEBUG: 03:38:19.523: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.KQY812/dev/bus/usb/001/001 152s ** (umockdev-run:4187): DEBUG: 03:38:19.523: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1a.0 152s ** (umockdev-run:4187): DEBUG: 03:38:19.524: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1a.0 (subsystem pci) 152s (process:4191): libfprint-context-DEBUG: 03:38:19.611: Initializing FpContext (libfprint version 1.94.8+tod1) 152s (process:4191): libfprint-tod-DEBUG: 03:38:19.611: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 152s (process:4191): libfprint-context-DEBUG: 03:38:19.614: No driver found for USB device 8087:0020 152s (process:4191): libfprint-context-DEBUG: 03:38:19.614: No driver found for USB device 1D6B:0002 152s (process:4191): libfprint-device-DEBUG: 03:38:19.614: Device reported probe completion 152s (process:4191): libfprint-device-DEBUG: 03:38:19.614: Completing action FPI_DEVICE_ACTION_PROBE in idle! 152s (process:4191): libfprint-device-DEBUG: 03:38:19.614: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 152s (process:4191): libfprint-image_device-DEBUG: 03:38:19.616: Image device open completed 152s (process:4191): libfprint-device-DEBUG: 03:38:19.616: Device reported open completion 152s (process:4191): libfprint-device-DEBUG: 03:38:19.616: Completing action FPI_DEVICE_ACTION_OPEN in idle! 152s (process:4191): libfprint-device-DEBUG: 03:38:19.616: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 152s (process:4191): libfprint-device-DEBUG: 03:38:19.616: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 152s (process:4191): libfprint-image_device-DEBUG: 03:38:19.616: Activating image device 152s (process:4191): libfprint-image_device-DEBUG: 03:38:19.616: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.616: [upektc_img] ACTIVATE_NUM_STATES entering state 0 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.617: [upektc_img] ACTIVATE_NUM_STATES entering state 1 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.618: [upektc_img] ACTIVATE_NUM_STATES entering state 2 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.619: [upektc_img] ACTIVATE_NUM_STATES entering state 3 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.621: [upektc_img] ACTIVATE_NUM_STATES entering state 4 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.622: [upektc_img] ACTIVATE_NUM_STATES entering state 5 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.623: [upektc_img] ACTIVATE_NUM_STATES entering state 6 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.624: [upektc_img] ACTIVATE_NUM_STATES entering state 7 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.624: [upektc_img] ACTIVATE_NUM_STATES entering state 8 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.625: [upektc_img] ACTIVATE_NUM_STATES entering state 9 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.626: [upektc_img] ACTIVATE_NUM_STATES entering state 10 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.627: [upektc_img] ACTIVATE_NUM_STATES entering state 11 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.628: Sensor type : TCS4x, width x height: 192 x 512 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.628: [upektc_img] ACTIVATE_NUM_STATES completed successfully 152s (process:4191): libfprint-image_device-DEBUG: 03:38:19.628: Image device activation completed 152s (process:4191): libfprint-image_device-DEBUG: 03:38:19.628: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 152s (process:4191): libfprint-image_device-DEBUG: 03:38:19.628: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 152s (process:4191): libfprint-device-DEBUG: 03:38:19.628: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.628: [upektc_img] CAPTURE_NUM_STATES entering state 0 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.629: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.630: request completed, len: 0040 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.630: 18th byte is 0c 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.630: [upektc_img] CAPTURE_NUM_STATES entering state 3 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.631: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.632: request completed, len: 0040 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.632: [upektc_img] CAPTURE_NUM_STATES entering state 4 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.634: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.635: request completed, len: 0040 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.635: 18th byte is 00 152s (process:4191): libfprint-device-DEBUG: 03:38:19.635: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.635: [upektc_img] CAPTURE_NUM_STATES entering state 3 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.635: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.636: request completed, len: 0040 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.636: response_size is 2052, actual_length is 64 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.636: Waiting for rest of transfer 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.636: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.637: request completed, len: 07c4 152s (process:4191): libfprint-image_device-DEBUG: 03:38:19.637: Image device reported finger status: on 152s (process:4191): libfprint-image_device-DEBUG: 03:38:19.637: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.637: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.637: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.638: request completed, len: 0040 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.638: response_size is 2052, actual_length is 64 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.638: Waiting for rest of transfer 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.638: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.638: request completed, len: 07c4 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.638: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.639: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.639: request completed, len: 0040 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.639: response_size is 2052, actual_length is 64 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.639: Waiting for rest of transfer 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.639: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.640: request completed, len: 07c4 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.640: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.641: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.641: request completed, len: 0040 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.641: response_size is 2052, actual_length is 64 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.641: Waiting for rest of transfer 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.641: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.642: request completed, len: 07c4 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.642: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.642: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.643: request completed, len: 0040 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.643: response_size is 2052, actual_length is 64 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.643: Waiting for rest of transfer 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.643: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.644: request completed, len: 07c4 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.644: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.644: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.645: request completed, len: 0040 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.645: response_size is 2052, actual_length is 64 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.645: Waiting for rest of transfer 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.645: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.646: request completed, len: 07c4 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.646: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.646: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.651: request completed, len: 0040 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.651: response_size is 2052, actual_length is 64 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.651: Waiting for rest of transfer 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.651: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.652: request completed, len: 07c4 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.652: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.653: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.653: request completed, len: 0040 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.653: response_size is 2052, actual_length is 64 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.653: Waiting for rest of transfer 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.653: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.654: request completed, len: 07c4 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.654: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.665: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.666: request completed, len: 0040 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.666: response_size is 2052, actual_length is 64 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.666: Waiting for rest of transfer 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.666: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.667: request completed, len: 07c4 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.667: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.667: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.668: request completed, len: 0040 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.668: response_size is 2052, actual_length is 64 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.668: Waiting for rest of transfer 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.668: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.668: request completed, len: 07c4 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.668: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.669: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.669: request completed, len: 0040 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.669: response_size is 2052, actual_length is 64 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.669: Waiting for rest of transfer 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.669: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.670: request completed, len: 07c4 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.670: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.671: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.672: request completed, len: 0040 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.672: response_size is 2052, actual_length is 64 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.672: Waiting for rest of transfer 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.672: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.672: request completed, len: 07c4 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.672: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.673: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.673: request completed, len: 0040 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.673: response_size is 2052, actual_length is 64 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.673: Waiting for rest of transfer 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.673: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.675: request completed, len: 07c4 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.675: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.676: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.676: request completed, len: 0040 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.676: response_size is 2052, actual_length is 64 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.676: Waiting for rest of transfer 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.676: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.677: request completed, len: 07c4 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.677: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.677: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.678: request completed, len: 0040 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.678: response_size is 2052, actual_length is 64 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.678: Waiting for rest of transfer 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.678: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.679: request completed, len: 07c4 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.679: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.679: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.680: request completed, len: 0040 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.680: response_size is 2052, actual_length is 64 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.680: Waiting for rest of transfer 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.680: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.680: request completed, len: 07c4 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.680: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.681: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.682: request completed, len: 0040 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.682: response_size is 2052, actual_length is 64 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.682: Waiting for rest of transfer 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.682: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.682: request completed, len: 07c4 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.682: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.683: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.684: request completed, len: 0040 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.684: response_size is 2052, actual_length is 64 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.684: Waiting for rest of transfer 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.684: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.684: request completed, len: 07c4 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.684: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.688: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.689: request completed, len: 0040 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.689: response_size is 2052, actual_length is 64 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.689: Waiting for rest of transfer 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.689: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.690: request completed, len: 07c4 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.690: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.691: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.692: request completed, len: 0040 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.692: response_size is 2052, actual_length is 64 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.692: Waiting for rest of transfer 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.692: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.693: request completed, len: 07c4 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.694: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.694: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.695: request completed, len: 0040 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.695: response_size is 2052, actual_length is 64 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.695: Waiting for rest of transfer 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.695: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.697: request completed, len: 07c4 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.697: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.698: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.699: request completed, len: 0040 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.699: response_size is 2052, actual_length is 64 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.699: Waiting for rest of transfer 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.699: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.700: request completed, len: 07c4 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.700: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.701: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.702: request completed, len: 0040 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.702: response_size is 2052, actual_length is 64 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.702: Waiting for rest of transfer 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.702: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.703: request completed, len: 07c4 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.703: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.703: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.704: request completed, len: 0040 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.704: response_size is 2052, actual_length is 64 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.704: Waiting for rest of transfer 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.704: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.705: request completed, len: 07c4 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.705: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.705: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.706: request completed, len: 0040 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.706: response_size is 2052, actual_length is 64 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.706: Waiting for rest of transfer 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.706: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.707: request completed, len: 07c4 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.707: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.708: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.709: request completed, len: 0040 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.709: response_size is 2052, actual_length is 64 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.709: Waiting for rest of transfer 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.709: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.709: request completed, len: 07c4 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.709: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.710: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.711: request completed, len: 0040 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.711: response_size is 2052, actual_length is 64 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.711: Waiting for rest of transfer 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.711: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.711: request completed, len: 07c4 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.711: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.712: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.713: request completed, len: 0040 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.713: response_size is 186, actual_length is 64 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.713: Waiting for rest of transfer 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.713: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.714: request completed, len: 007a 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.714: Image size is 55296 152s (process:4191): libfprint-image_device-DEBUG: 03:38:19.714: Image device captured an image 152s (process:4191): libfprint-image_device-DEBUG: 03:38:19.714: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 152s (process:4191): libfprint-device-DEBUG: 03:38:19.716: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:4191): libfprint-device-DEBUG: 03:38:19.716: Device reported finger status change: FP_FINGER_STATUS_NONE 152s (process:4191): libfprint-image_device-DEBUG: 03:38:19.716: Image device reported finger status: off 152s (process:4191): libfprint-image_device-DEBUG: 03:38:19.716: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 152s (process:4191): libfprint-image_device-DEBUG: 03:38:19.716: Deactivating image device 152s (process:4191): libfprint-image_device-DEBUG: 03:38:19.716: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.716: [upektc_img] CAPTURE_NUM_STATES completed successfully 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.716: [upektc_img] DEACTIVATE_NUM_STATES entering state 0 152s (process:4191): libfprint-device-DEBUG: 03:38:19.719: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.719: [upektc_img] DEACTIVATE_NUM_STATES entering state 1 152s (process:4191): libfprint-SSM-DEBUG: 03:38:19.720: [upektc_img] DEACTIVATE_NUM_STATES completed successfully 152s (process:4191): libfprint-upektc_img-DEBUG: 03:38:19.720: Deactivate completed 152s (process:4191): libfprint-image_device-DEBUG: 03:38:19.720: Image device deactivation completed 152s (process:4191): libfprint-image_device-DEBUG: 03:38:19.720: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 152s (process:4191): libfprint-image-DEBUG: 03:38:19.727: Minutiae scan completed in 0.013034 secs 152s (process:4191): libfprint-device-DEBUG: 03:38:19.727: Device reported capture completion 152s (process:4191): libfprint-device-DEBUG: 03:38:19.727: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 152s (process:4191): libfprint-device-DEBUG: 03:38:19.727: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 152s (process:4191): libfprint-image_device-DEBUG: 03:38:19.728: Image device close completed 152s (process:4191): libfprint-device-DEBUG: 03:38:19.728: Device reported close completion 152s (process:4191): libfprint-device-DEBUG: 03:38:19.728: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 152s (process:4191): libfprint-device-DEBUG: 03:38:19.728: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 152s ** (umockdev-run:4187): DEBUG: 03:38:19.838: umockdev.vala:154: Removing test bed /tmp/umockdev.KQY812 152s (umockdev-run:4187): GLib-DEBUG: 03:38:19.845: unsetenv() is not thread-safe and should not be used after threads are created 152s Comparing PNGs /tmp/libfprint-umockdev-test-g0z7xjhn/capture.png and /usr/share/installed-tests/libfprint-2/upektc_img/capture.png 152s PASS: libfprint-2/driver-upektc_img.test 152s Running test: libfprint-2/driver-egismoc-0587.test 152s ** (umockdev-run:4200): DEBUG: 03:38:19.909: umockdev.vala:127: Created udev test bed /tmp/umockdev.RW8G22 152s ** (umockdev-run:4200): DEBUG: 03:38:19.909: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3/3-5 152s ** (umockdev-run:4200): DEBUG: 03:38:19.911: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3/3-5 (subsystem usb) 152s ** (umockdev-run:4200): DEBUG: 03:38:19.915: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.RW8G22/dev/bus/usb/003/009 152s ** (umockdev-run:4200): DEBUG: 03:38:19.915: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3 152s ** (umockdev-run:4200): DEBUG: 03:38:19.916: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3 (subsystem usb) 152s ** (umockdev-run:4200): DEBUG: 03:38:19.919: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.RW8G22/dev/bus/usb/003/001 152s ** (umockdev-run:4200): DEBUG: 03:38:19.919: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 152s ** (umockdev-run:4200): DEBUG: 03:38:19.920: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 153s (process:4204): libfprint-context-DEBUG: 03:38:20.010: Initializing FpContext (libfprint version 1.94.8+tod1) 153s (process:4204): libfprint-tod-DEBUG: 03:38:20.010: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.013: 99820699: ../libfprint/drivers/egismoc/egismoc.c:1597 153s (process:4204): libfprint-context-DEBUG: 03:38:20.013: No driver found for USB device 1D6B:0002 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.013: egismoc_probe enter --> 153s (process:4204): libfprint-device-DEBUG: 03:38:20.015: Device reported probe completion 153s (process:4204): libfprint-device-DEBUG: 03:38:20.015: Completing action FPI_DEVICE_ACTION_PROBE in idle! 153s (process:4204): libfprint-device-DEBUG: 03:38:20.015: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.016: Opening device 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.016: [egismoc] DEV_INIT_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.017: [egismoc] DEV_INIT_STATES entering state 1 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.018: [egismoc] DEV_INIT_STATES entering state 2 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.018: [egismoc] DEV_INIT_STATES entering state 3 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.019: [egismoc] DEV_INIT_STATES entering state 4 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.020: [egismoc] DEV_INIT_STATES entering state 5 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.020: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.020: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.020: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.021: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.022: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.022: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.022: Firmware version callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.022: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.022: Device firmware version is 9050.6.4.67 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.022: [egismoc] DEV_INIT_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.022: Task SSM done 153s (process:4204): libfprint-device-DEBUG: 03:38:20.022: Device reported open completion 153s (process:4204): libfprint-device-DEBUG: 03:38:20.022: Completing action FPI_DEVICE_ACTION_OPEN in idle! 153s (process:4204): libfprint-device-DEBUG: 03:38:20.022: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.023: List 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.023: [egismoc] LIST_STATES entering state 0 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.023: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.023: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.023: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.024: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.024: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.024: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.024: List callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.024: Device fingerprint 1: FP1-00000000-2-00000000-nobody 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.024: Number of currently enrolled fingerprints on the device is 1 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.024: [egismoc] LIST_STATES entering state 1 153s (process:4204): libfprint-device-DEBUG: 03:38:20.025: Device reported listing completion 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.025: [egismoc] LIST_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.025: Task SSM done 153s (process:4204): libfprint-device-DEBUG: 03:38:20.025: Completing action FPI_DEVICE_ACTION_LIST in idle! 153s (process:4204): libfprint-device-DEBUG: 03:38:20.025: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.025: Clear storage 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.025: [egismoc] DELETE_STATES entering state 0 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.025: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.025: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.025: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.025: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.026: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.026: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.026: List callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.026: Device fingerprint 1: FP1-00000000-2-00000000-nobody 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.026: Number of currently enrolled fingerprints on the device is 1 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.026: [egismoc] DELETE_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.026: Get delete command 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.026: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.026: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.026: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.027: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.028: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.028: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.028: Delete callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.028: Response prefix valid: yes 153s (process:4204): libfprint-device-DEBUG: 03:38:20.028: Device reported deletion completion 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.028: [egismoc] DELETE_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.028: Task SSM done 153s (process:4204): libfprint-device-DEBUG: 03:38:20.028: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 153s (process:4204): libfprint-device-DEBUG: 03:38:20.028: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.028: List 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.028: [egismoc] LIST_STATES entering state 0 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.028: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.028: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.028: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.029: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.030: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.030: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.030: List callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.030: Number of currently enrolled fingerprints on the device is 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.030: [egismoc] LIST_STATES entering state 1 153s (process:4204): libfprint-device-DEBUG: 03:38:20.030: Device reported listing completion 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.030: [egismoc] LIST_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.030: Task SSM done 153s (process:4204): libfprint-device-DEBUG: 03:38:20.030: Completing action FPI_DEVICE_ACTION_LIST in idle! 153s (process:4204): libfprint-device-DEBUG: 03:38:20.030: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s (process:4204): libfprint-device-DEBUG: 03:38:20.031: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.031: Enroll 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.031: [egismoc] ENROLL_STATES entering state 0 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.031: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.031: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.031: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.032: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.032: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.032: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.032: List callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.032: Number of currently enrolled fingerprints on the device is 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.032: [egismoc] ENROLL_STATES entering state 1 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.032: [egismoc] ENROLL_STATES entering state 2 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.032: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.032: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.032: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.033: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.034: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.034: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.034: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.034: [egismoc] ENROLL_STATES entering state 3 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.034: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.034: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.034: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.035: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.035: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.035: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.035: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.036: [egismoc] ENROLL_STATES entering state 4 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.036: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.036: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.036: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.036: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.036: [egismoc] ENROLL_STATES entering state 5 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.036: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.036: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.036: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.037: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.038: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.038: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.038: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.038: [egismoc] ENROLL_STATES entering state 6 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.038: Get check command 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.038: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.038: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.038: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.038: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.039: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.039: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.039: Enroll check callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.039: Response suffix valid: yes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.039: [egismoc] ENROLL_STATES entering state 7 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.039: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.039: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.039: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.040: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.041: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.041: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.041: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.041: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.041: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.041: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.041: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.041: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.043: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.043: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.043: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.043: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.043: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.043: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.043: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.043: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.044: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.044: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.044: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.044: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.044: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.044: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.045: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.045: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.045: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.045: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.045: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.045: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.045: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.046: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.046: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.046: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.046: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.046: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.046: Partial capture successful. Please touch the sensor again (1/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.046: Device reported enroll progress, reported 1 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.046: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.046: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.046: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.046: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.047: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.047: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.047: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.047: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.047: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.047: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.047: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.047: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.048: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.049: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.049: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.049: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.049: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.049: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.049: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.049: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.049: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.049: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.049: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.049: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.049: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.050: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.051: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.051: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.051: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.051: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.051: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.051: Partial capture successful. Please touch the sensor again (2/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.051: Device reported enroll progress, reported 2 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.051: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.051: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.051: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.051: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.051: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.052: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.052: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.052: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.052: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.052: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.052: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.052: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.053: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.053: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.053: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.053: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.053: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.053: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.053: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.054: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.054: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.054: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.054: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.054: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.054: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.055: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.055: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.055: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.055: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.055: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.055: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.055: Partial capture successful. Please touch the sensor again (3/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.055: Device reported enroll progress, reported 3 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.055: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.055: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.055: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.055: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.056: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.056: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.056: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.057: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.057: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.057: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.057: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.057: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.057: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.058: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.058: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.058: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.058: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.058: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.058: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.058: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.058: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.058: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.058: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.058: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.058: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.059: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.060: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.060: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.060: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.060: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.060: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.060: Partial capture successful. Please touch the sensor again (4/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.060: Device reported enroll progress, reported 4 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.060: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.060: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.060: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.060: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.060: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.061: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.061: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.061: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.061: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.061: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.061: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.061: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.062: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.062: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.062: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.062: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.062: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.062: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.062: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.063: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.063: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.063: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.063: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.063: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.063: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.064: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.064: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.064: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.064: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.064: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.064: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.064: Partial capture successful. Please touch the sensor again (5/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.064: Device reported enroll progress, reported 5 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.064: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.064: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.064: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.065: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.065: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.066: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.066: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.066: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.066: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.066: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.066: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.066: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.067: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.067: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.067: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.067: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.067: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.067: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.067: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.068: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.068: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.068: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.068: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.068: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.068: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.069: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.070: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.070: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.070: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.070: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.070: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.070: Partial capture successful. Please touch the sensor again (6/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.070: Device reported enroll progress, reported 6 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.070: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.070: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.070: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.070: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.070: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.071: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.071: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.071: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.071: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.071: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.071: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.071: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.071: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.074: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.074: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.074: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.074: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.074: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.074: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.074: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.074: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.074: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.074: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.074: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.074: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.076: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.076: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.076: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.076: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.076: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.076: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.076: Partial capture successful. Please touch the sensor again (7/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.076: Device reported enroll progress, reported 7 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.076: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.076: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.076: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.076: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.077: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.077: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.077: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.077: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.077: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.077: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.077: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.077: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.078: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.079: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.079: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.079: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.079: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.079: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.079: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.080: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.080: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.080: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.080: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.080: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.080: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.080: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.081: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.081: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.081: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.081: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.081: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.081: Partial capture successful. Please touch the sensor again (8/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.081: Device reported enroll progress, reported 8 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.081: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.081: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.081: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.081: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.081: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.082: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.082: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.082: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.082: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.082: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.082: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.082: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.083: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.083: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.083: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.083: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.083: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.083: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.083: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.084: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.084: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.084: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.084: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.084: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.084: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.085: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.086: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.086: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.086: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.086: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.086: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.086: Partial capture successful. Please touch the sensor again (9/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.086: Device reported enroll progress, reported 9 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.086: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.086: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.086: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.086: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.087: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.087: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.087: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.087: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.087: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.087: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.087: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.087: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.088: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.088: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.088: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.088: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.088: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.088: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.088: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.089: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.089: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.089: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.089: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.089: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.089: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.090: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.090: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.090: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.090: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.090: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.090: Response suffix valid: NO 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.090: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.090: Response suffix valid: yes 153s (process:4204): libfprint-device-DEBUG: 03:38:20.090: Device reported enroll progress, reported 9 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.090: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.090: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.091: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.091: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.091: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.092: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.092: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.092: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.092: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.092: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.092: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.092: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.092: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.093: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.093: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.093: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.093: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.093: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.093: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.093: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.093: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.093: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.093: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.093: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.093: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.094: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.095: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.095: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.095: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.095: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.095: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.095: Partial capture successful. Please touch the sensor again (10/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.095: Device reported enroll progress, reported 10 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.095: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.095: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.095: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.095: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.095: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.096: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.096: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.096: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.096: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.096: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.096: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.096: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.096: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.097: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.097: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.097: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.097: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.097: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.097: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.099: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.099: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.099: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.099: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.099: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.099: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.100: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.103: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.103: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.103: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.103: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.103: Response suffix valid: NO 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.103: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.103: Response suffix valid: yes 153s (process:4204): libfprint-device-DEBUG: 03:38:20.103: Device reported enroll progress, reported 10 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.103: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.103: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.103: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.103: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.103: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.104: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.104: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.104: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.104: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.104: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.104: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.104: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.104: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.105: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.105: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.105: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.105: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.105: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.105: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.106: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.106: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.106: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.106: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.106: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.106: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.106: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.107: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.107: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.107: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.107: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.107: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.107: Partial capture successful. Please touch the sensor again (11/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.107: Device reported enroll progress, reported 11 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.107: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.107: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.107: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.107: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.107: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.108: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.108: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.108: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.108: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.108: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.108: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.108: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.109: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.109: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.109: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.109: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.109: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.109: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.109: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.110: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.110: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.110: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.110: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.110: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.110: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.111: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.111: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.111: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.111: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.111: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.111: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.111: Partial capture successful. Please touch the sensor again (12/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.111: Device reported enroll progress, reported 12 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.111: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.111: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.111: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.111: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.115: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.116: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.116: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.116: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.116: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.116: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.116: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.116: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.116: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.117: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.117: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.117: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.117: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.117: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.117: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.118: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.118: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.118: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.118: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.118: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.118: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.119: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.120: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.120: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.120: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.120: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.120: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.120: Partial capture successful. Please touch the sensor again (13/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.120: Device reported enroll progress, reported 13 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.120: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.120: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.120: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.120: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.120: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.121: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.121: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.121: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.121: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.121: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.121: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.121: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.122: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.122: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.122: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.122: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.122: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.122: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.122: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.123: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.123: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.123: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.123: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.123: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.123: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.123: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.124: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.124: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.124: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.124: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.124: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.124: Partial capture successful. Please touch the sensor again (14/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.124: Device reported enroll progress, reported 14 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.124: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.124: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.124: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.124: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.125: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.125: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.125: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.125: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.125: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.125: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.125: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.125: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.126: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.126: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.126: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.126: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.126: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.126: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.126: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.127: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.127: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.127: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.127: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.127: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.127: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.128: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.128: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.128: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.128: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.128: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.128: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.128: Partial capture successful. Please touch the sensor again (15/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.128: Device reported enroll progress, reported 15 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.128: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.128: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.128: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.128: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.129: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.129: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.129: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.129: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.129: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.129: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.129: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.129: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.130: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.131: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.131: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.131: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.131: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.131: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.131: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.131: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.131: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.131: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.131: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.131: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.131: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.132: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-device-DEBUG: 03:38:20.132: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.133: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.133: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.133: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.133: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.133: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.133: Partial capture successful. Please touch the sensor again (16/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.133: Device reported enroll progress, reported 16 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.133: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.133: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.133: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.133: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.133: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.134: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.134: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.134: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.134: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.134: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.134: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.134: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.134: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.135: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.135: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.135: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.135: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.135: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.135: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.136: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.136: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.136: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.136: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.136: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.136: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.137: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.138: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.138: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.138: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.138: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.138: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.138: Partial capture successful. Please touch the sensor again (17/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.138: Device reported enroll progress, reported 17 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.138: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.138: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.138: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.138: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.139: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.139: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.139: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.139: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.139: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.139: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.139: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.139: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.141: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.142: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.142: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.142: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.142: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.142: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.142: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.143: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.143: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.143: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.143: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.143: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.143: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.144: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.145: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.145: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.145: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.145: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.145: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.145: Partial capture successful. Please touch the sensor again (18/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.145: Device reported enroll progress, reported 18 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.145: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.145: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.145: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.145: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.145: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.146: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.146: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.146: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.146: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.146: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.146: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.146: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.147: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.148: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.148: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.148: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.148: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.148: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.148: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.148: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.148: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.149: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.149: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.149: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.149: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.149: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.150: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.150: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.150: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.150: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.150: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.150: Partial capture successful. Please touch the sensor again (19/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.150: Device reported enroll progress, reported 19 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.150: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.150: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.150: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.150: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.150: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.151: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.151: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.151: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.151: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.151: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.151: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.151: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.152: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.155: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.155: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.155: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.155: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.155: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.155: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.155: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.155: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.155: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.155: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.155: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.155: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.156: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.156: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.156: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.156: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.156: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.156: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.156: Partial capture successful. Please touch the sensor again (20/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.156: Device reported enroll progress, reported 20 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.157: [egismoc] ENROLL_STATES entering state 12 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.157: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.157: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.157: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.157: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.158: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.158: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.158: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.158: [egismoc] ENROLL_STATES entering state 13 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.158: New fingerprint ID: FP1-00000000-2-00000000-nobody 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.158: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.158: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.158: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.158: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.159: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.159: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.159: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.159: [egismoc] ENROLL_STATES entering state 14 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.159: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.159: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.159: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.159: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.160: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.160: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.160: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.160: [egismoc] ENROLL_STATES entering state 15 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.160: Enrollment was successful! 153s (process:4204): libfprint-device-DEBUG: 03:38:20.160: Device reported enroll completion 153s (process:4204): libfprint-device-DEBUG: 03:38:20.160: Device reported finger status change: FP_FINGER_STATUS_NONE 153s (process:4204): libfprint-device-DEBUG: 03:38:20.160: Print for finger FP_FINGER_LEFT_INDEX enrolled 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.160: [egismoc] ENROLL_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.160: Task SSM done 153s (process:4204): libfprint-device-DEBUG: 03:38:20.160: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 153s (process:4204): libfprint-device-DEBUG: 03:38:20.160: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.160: List 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.160: [egismoc] LIST_STATES entering state 0 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.160: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.160: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.160: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.161: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.161: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.161: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.161: List callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.161: Device fingerprint 1: FP1-00000000-2-00000000-nobody 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.161: Number of currently enrolled fingerprints on the device is 1 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.161: [egismoc] LIST_STATES entering state 1 153s (process:4204): libfprint-device-DEBUG: 03:38:20.161: Device reported listing completion 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.161: [egismoc] LIST_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.161: Task SSM done 153s (process:4204): libfprint-device-DEBUG: 03:38:20.162: Completing action FPI_DEVICE_ACTION_LIST in idle! 153s (process:4204): libfprint-device-DEBUG: 03:38:20.162: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 153s (process:4204): libfprint-device-DEBUG: 03:38:20.162: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.162: Identify or Verify 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.162: [egismoc] IDENTIFY_STATES entering state 0 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.162: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.162: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.162: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.162: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.163: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.163: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.163: List callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.163: Device fingerprint 1: FP1-00000000-2-00000000-nobody 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.163: Number of currently enrolled fingerprints on the device is 1 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.163: [egismoc] IDENTIFY_STATES entering state 1 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.163: [egismoc] IDENTIFY_STATES entering state 2 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.163: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.163: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.163: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.164: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.164: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.164: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.164: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.164: [egismoc] IDENTIFY_STATES entering state 3 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.164: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.164: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.164: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.165: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.165: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.165: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.165: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.166: [egismoc] IDENTIFY_STATES entering state 4 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.166: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.166: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.166: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.166: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.166: [egismoc] IDENTIFY_STATES entering state 5 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.166: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.166: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.166: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.167: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.167: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.167: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.167: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.167: [egismoc] IDENTIFY_STATES entering state 6 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.167: Get check command 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.167: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.167: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.167: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.168: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.168: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.168: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.168: Identify check callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.168: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.168: Identify successful for: FP1-00000000-2-00000000-nobody 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.168: Verifying against: FP1-00000000-2-00000000-nobody 153s (process:4204): libfprint-device-DEBUG: 03:38:20.168: Device reported verify result 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.168: [egismoc] IDENTIFY_STATES entering state 7 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.168: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.168: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.168: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.169: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.170: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.170: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.170: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.170: [egismoc] IDENTIFY_STATES entering state 8 153s (process:4204): libfprint-device-DEBUG: 03:38:20.170: Device reported verify completion 153s (process:4204): libfprint-device-DEBUG: 03:38:20.170: Device reported finger status change: FP_FINGER_STATUS_NONE 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.170: [egismoc] IDENTIFY_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.170: Task SSM done 153s (process:4204): libfprint-device-DEBUG: 03:38:20.170: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 153s (process:4204): libfprint-device-DEBUG: 03:38:20.170: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 153s (process:4204): libfprint-device-DEBUG: 03:38:20.170: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.170: Identify or Verify 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.170: [egismoc] IDENTIFY_STATES entering state 0 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.170: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.170: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.170: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.171: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.175: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.175: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.175: List callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.175: Device fingerprint 1: FP1-00000000-2-00000000-nobody 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.175: Number of currently enrolled fingerprints on the device is 1 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.176: [egismoc] IDENTIFY_STATES entering state 1 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.176: [egismoc] IDENTIFY_STATES entering state 2 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.176: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.176: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.176: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.176: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.177: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.177: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.177: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.177: [egismoc] IDENTIFY_STATES entering state 3 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.177: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.177: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.177: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.177: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.179: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.179: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.179: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.179: [egismoc] IDENTIFY_STATES entering state 4 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.179: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.179: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.179: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.179: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.179: [egismoc] IDENTIFY_STATES entering state 5 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.179: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.179: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.179: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.180: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.181: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.181: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.181: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.181: [egismoc] IDENTIFY_STATES entering state 6 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.181: Get check command 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.181: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.181: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.181: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.182: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.183: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.183: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.183: Identify check callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.183: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.183: Identify successful for: FP1-00000000-2-00000000-nobody 153s (process:4204): libfprint-device-DEBUG: 03:38:20.183: Device reported identify result 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.183: [egismoc] IDENTIFY_STATES entering state 7 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.183: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.183: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.183: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.183: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.184: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.184: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.184: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.184: [egismoc] IDENTIFY_STATES entering state 8 153s (process:4204): libfprint-device-DEBUG: 03:38:20.184: Device reported identify completion 153s (process:4204): libfprint-device-DEBUG: 03:38:20.184: Device reported finger status change: FP_FINGER_STATUS_NONE 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.184: [egismoc] IDENTIFY_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.184: Task SSM done 153s (process:4204): libfprint-device-DEBUG: 03:38:20.184: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 153s (process:4204): libfprint-device-DEBUG: 03:38:20.184: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 153s (process:4204): libfprint-device-DEBUG: 03:38:20.184: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.184: Enroll 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.184: [egismoc] ENROLL_STATES entering state 0 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.184: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.184: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.184: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.185: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.186: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.186: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.186: List callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.186: Device fingerprint 1: FP1-00000000-2-00000000-nobody 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.186: Number of currently enrolled fingerprints on the device is 1 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.186: [egismoc] ENROLL_STATES entering state 1 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.186: [egismoc] ENROLL_STATES entering state 2 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.186: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.186: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.186: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.187: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.187: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.187: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.187: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.187: [egismoc] ENROLL_STATES entering state 3 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.187: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.187: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.187: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.188: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.189: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.189: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.189: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.189: [egismoc] ENROLL_STATES entering state 4 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.189: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.189: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.190: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.190: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.190: [egismoc] ENROLL_STATES entering state 5 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.190: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.190: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.190: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.190: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.191: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.191: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.191: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.191: [egismoc] ENROLL_STATES entering state 6 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.191: Get check command 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.191: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.191: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.191: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.191: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.192: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.192: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.192: Enroll check callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.192: Response suffix valid: NO 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.192: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.192: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.192: Task SSM done 153s (process:4204): libfprint-device-DEBUG: 03:38:20.192: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL 153s (process:4204): libfprint-device-DEBUG: 03:38:20.192: Device reported enroll completion 153s (process:4204): libfprint-device-DEBUG: 03:38:20.192: Device reported finger status change: FP_FINGER_STATUS_NONE 153s (process:4204): libfprint-device-DEBUG: 03:38:20.192: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 153s (process:4204): libfprint-device-DEBUG: 03:38:20.192: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.192: List 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.192: [egismoc] LIST_STATES entering state 0 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.192: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.192: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.192: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.193: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.195: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.195: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.195: List callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.195: Device fingerprint 1: FP1-00000000-2-00000000-nobody 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.195: Number of currently enrolled fingerprints on the device is 1 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.195: [egismoc] LIST_STATES entering state 1 153s (process:4204): libfprint-device-DEBUG: 03:38:20.195: Device reported listing completion 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.195: [egismoc] LIST_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.195: Task SSM done 153s (process:4204): libfprint-device-DEBUG: 03:38:20.195: Completing action FPI_DEVICE_ACTION_LIST in idle! 153s (process:4204): libfprint-device-DEBUG: 03:38:20.195: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 153s (process:4204): libfprint-device-DEBUG: 03:38:20.195: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.195: Enroll 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.195: [egismoc] ENROLL_STATES entering state 0 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.195: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.195: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.195: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.196: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.197: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.197: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.197: List callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.197: Device fingerprint 1: FP1-00000000-2-00000000-nobody 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.197: Number of currently enrolled fingerprints on the device is 1 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.197: [egismoc] ENROLL_STATES entering state 1 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.197: [egismoc] ENROLL_STATES entering state 2 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.197: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.197: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.197: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.198: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.199: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.199: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.199: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.199: [egismoc] ENROLL_STATES entering state 3 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.199: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.199: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.199: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.199: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.200: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.200: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.200: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.200: [egismoc] ENROLL_STATES entering state 4 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.200: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.200: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.201: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.201: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.201: [egismoc] ENROLL_STATES entering state 5 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.201: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.201: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.201: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.201: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.202: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.202: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.202: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.202: [egismoc] ENROLL_STATES entering state 6 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.202: Get check command 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.202: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.202: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.202: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.203: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.203: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.203: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.203: Enroll check callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.203: Response suffix valid: yes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.203: [egismoc] ENROLL_STATES entering state 7 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.203: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.203: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.203: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.204: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.205: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.205: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.205: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.205: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.205: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.205: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.205: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.205: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.206: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.206: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.206: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.206: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.206: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.206: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.206: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.206: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.207: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.207: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.207: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.207: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.207: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.207: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.208: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.208: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.208: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.208: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.208: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.208: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.208: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.209: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.209: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.209: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.209: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.209: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.209: Partial capture successful. Please touch the sensor again (1/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.209: Device reported enroll progress, reported 1 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.209: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.209: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.209: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.209: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.209: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.210: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.210: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.210: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.210: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.210: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.210: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.210: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.211: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.211: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.211: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.211: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.211: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.211: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.211: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.212: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.212: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.212: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.212: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.212: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.212: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.213: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.213: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.213: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.213: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.213: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.213: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.213: Partial capture successful. Please touch the sensor again (2/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.213: Device reported enroll progress, reported 2 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.213: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.213: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.213: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.213: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.214: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.215: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.215: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.215: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.215: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.215: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.215: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.215: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.215: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.216: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.216: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.216: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.216: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.216: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.216: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.217: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.217: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.217: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.217: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.217: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.217: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.218: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.219: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.219: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.219: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.219: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.219: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.219: Partial capture successful. Please touch the sensor again (3/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.219: Device reported enroll progress, reported 3 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.219: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.219: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.219: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.219: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.219: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.220: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.220: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.220: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.220: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.220: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.220: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.220: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.220: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.221: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.221: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.221: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.221: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.221: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.221: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.222: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.222: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.222: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.222: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.222: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.222: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.222: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.223: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.223: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.223: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.223: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.223: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.223: Partial capture successful. Please touch the sensor again (4/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.223: Device reported enroll progress, reported 4 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.223: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.223: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.223: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.223: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.224: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.225: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.225: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.225: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.225: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.225: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.225: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.225: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.226: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.226: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.226: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.226: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.226: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.226: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.226: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.227: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.227: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.227: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.227: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.227: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.227: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.228: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.228: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.228: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.228: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.228: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.229: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.229: Partial capture successful. Please touch the sensor again (5/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.229: Device reported enroll progress, reported 5 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.229: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.229: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.229: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.229: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.229: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.230: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.230: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.230: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.230: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.230: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.230: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.230: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.230: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.231: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.231: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.231: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.231: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.231: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.231: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.232: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.232: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.232: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.232: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.232: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.232: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.232: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.233: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.233: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.233: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.233: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.233: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.233: Partial capture successful. Please touch the sensor again (6/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.233: Device reported enroll progress, reported 6 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.233: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.233: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.233: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.233: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.234: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.234: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.234: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.234: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.234: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.234: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.234: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.234: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.235: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.236: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.236: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.236: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.236: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.236: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.236: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.237: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.237: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.237: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.237: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.237: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.237: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.237: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.238: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.238: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.238: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.238: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.238: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.238: Partial capture successful. Please touch the sensor again (7/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.238: Device reported enroll progress, reported 7 of 20 have been completed 153s listing - device should have prints 153s clear device storage 153s clear done 153s listing - device should be empty 153s enrolling 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 1, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 2, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 3, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 4, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 5, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 6, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 7, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 8, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 9, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 10, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 10, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 11, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 12, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 13, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 14, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 15, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 16, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 17, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 18, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 19, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 20, , None, None) 153s enroll done 153s listing - device should have 1 print 153s verifying 153s verify done 153s async identifying 153s indentification_done: 153s try to enroll duplicate 153s duplicate enroll attempt done 153s listing - device should still only have 1 print 153s enroll new finger 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 1, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 2, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 3, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 4, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 5, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 6, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 7, , None, None)(process:4204): libfprint-SSM-DEBUG: 03:38:20.238: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.238: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.238: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.238: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.238: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.239: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.239: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.239: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.239: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.239: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.239: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.239: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.240: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.240: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.240: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.240: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.240: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.240: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.240: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.241: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.241: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.241: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.241: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.241: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.241: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.241: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.243: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.243: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.243: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.243: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.243: Response suffix valid: NO 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.243: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.243: Response suffix valid: yes 153s (process:4204): libfprint-device-DEBUG: 03:38:20.243: Device reported enroll progress, reported 7 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.243: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.243: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.243: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.243: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.243: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.244: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.244: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.244: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.244: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.244: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.244: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.244: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.244: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.245: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.245: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.245: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.245: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.245: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.245: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.246: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.246: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.246: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.246: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.246: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.246: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.247: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.247: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.247: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.247: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.247: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.248: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.248: Partial capture successful. Please touch the sensor again (8/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.248: Device reported enroll progress, reported 8 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.248: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.248: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.248: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.248: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.248: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.249: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.249: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.249: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.249: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.249: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.249: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.249: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.250: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.250: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.250: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.250: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.250: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.250: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.250: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.251: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.251: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.251: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.251: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.251: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.251: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.255: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.255: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.255: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.255: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.255: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.255: Response suffix valid: NO 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.255: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.255: Response suffix valid: yes 153s (process:4204): libfprint-device-DEBUG: 03:38:20.255: Device reported enroll progress, reported 8 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.255: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.255: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.255: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.255: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.257: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.257: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.257: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.257: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.257: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.257: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.257: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.257: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.258: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.258: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.258: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.258: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.258: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.258: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.258: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.259: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.259: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.259: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.259: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.259: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.259: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.260: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.260: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.260: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.260: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.260: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.260: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.260: Partial capture successful. Please touch the sensor again (9/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.260: Device reported enroll progress, reported 9 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.260: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.260: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.260: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.260: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.261: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.262: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.262: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.262: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.262: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.262: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.262: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.262: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.262: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.263: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.263: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.263: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.263: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.263: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.263: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.264: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.264: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.264: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.264: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.264: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.264: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.264: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.265: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.265: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.265: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.265: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.265: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.265: Partial capture successful. Please touch the sensor again (10/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.265: Device reported enroll progress, reported 10 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.265: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.265: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.265: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.265: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.266: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.267: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.267: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.267: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.267: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.267: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.267: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.267: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.267: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.269: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.269: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.269: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.269: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.269: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.269: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.269: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.269: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.269: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.269: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.269: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.269: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.270: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.270: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.270: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.270: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.270: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.271: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.271: Partial capture successful. Please touch the sensor again (11/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.271: Device reported enroll progress, reported 11 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.271: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.271: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.271: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.271: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.271: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.272: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.272: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.272: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.272: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.272: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.272: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.272: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.272: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.273: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.273: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.273: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.273: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.273: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.273: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.273: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.273: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.273: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.273: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.273: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.273: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.274: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.275: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.275: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.275: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.275: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.275: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.275: Partial capture successful. Please touch the sensor again (12/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.275: Device reported enroll progress, reported 12 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.275: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.275: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.275: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.275: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.275: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.276: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.276: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.276: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.276: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.276: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.276: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.276: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.279: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.280: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.280: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.280: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.280: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.280: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.280: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.280: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.280: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.280: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.280: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.280: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.281: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.281: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.282: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.282: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.282: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.282: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.282: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.282: Partial capture successful. Please touch the sensor again (13/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.282: Device reported enroll progress, reported 13 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.282: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.282: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.282: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.282: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.282: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.283: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.283: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.283: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.283: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.283: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.283: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.283: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.283: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.284: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.284: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.284: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.284: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.284: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.284: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.285: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.285: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.285: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.285: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.285: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.285: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.285: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.286: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.286: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.286: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.286: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.286: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.286: Partial capture successful. Please touch the sensor again (14/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.286: Device reported enroll progress, reported 14 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.286: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.286: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.286: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.286: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.286: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.287: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.287: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.287: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.287: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.287: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.287: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.287: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.288: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.288: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.288: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.288: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.288: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.288: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.289: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.289: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.289: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.289: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.289: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.289: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.289: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.291: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.291: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.291: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.291: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.291: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.291: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.291: Partial capture successful. Please touch the sensor again (15/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.291: Device reported enroll progress, reported 15 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.292: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.292: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.292: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.292: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.292: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.293: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.293: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.293: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.293: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.293: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.293: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.293: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.293: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.294: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.294: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.294: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.294: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.294: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.294: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.295: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.295: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.295: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.295: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.295: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.295: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.295: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.296: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.296: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.296: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.296: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.296: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.296: Partial capture successful. Please touch the sensor again (16/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.296: Device reported enroll progress, reported 16 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.296: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.296: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.296: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.296: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.296: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.297: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.297: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.297: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.297: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.297: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.297: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.297: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.298: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.298: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.298: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.298: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.298: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.298: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.298: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.299: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.299: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.299: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.299: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.299: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.299: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.299: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.300: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.300: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.300: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.300: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.300: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.300: Partial capture successful. Please touch the sensor again (17/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.300: Device reported enroll progress, reported 17 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.300: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.300: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.300: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.300: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.301: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.301: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.301: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.301: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.301: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.301: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.301: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.301: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.302: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.302: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.302: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.302: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.302: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.302: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.303: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.303: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.303: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.303: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.303: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.303: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.303: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.304: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.304: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.304: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.304: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.304: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.304: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.304: Partial capture successful. Please touch the sensor again (18/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.304: Device reported enroll progress, reported 18 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.304: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.304: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.304: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.304: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.305: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.305: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.305: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.305: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.305: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.305: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.305: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.305: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.306: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.307: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.307: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.307: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.307: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.307: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.307: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.307: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.307: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.307: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.307: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.307: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.307: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.308: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.308: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.308: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.309: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.309: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.309: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.309: Partial capture successful. Please touch the sensor again (19/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.309: Device reported enroll progress, reported 19 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.309: [egismoc] ENROLL_STATES entering state 8 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.309: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.309: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.309: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.310: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.310: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.310: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.310: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.310: [egismoc] ENROLL_STATES entering state 9 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.310: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.310: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.310: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.311: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.312: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.312: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.312: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.312: [egismoc] ENROLL_STATES entering state 10 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.312: Wait for finger on sensor 153s (process:4204): libfprint-device-DEBUG: 03:38:20.312: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.313: Finger on sensor callback 153s (process:4204): libfprint-device-DEBUG: 03:38:20.313: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.313: [egismoc] ENROLL_STATES entering state 11 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.313: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.313: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.313: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.314: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.314: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.315: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.315: Read capture callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.315: Response prefix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.315: Response suffix valid: yes 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.315: Partial capture successful. Please touch the sensor again (20/20) 153s (process:4204): libfprint-device-DEBUG: 03:38:20.315: Device reported enroll progress, reported 20 of 20 have been completed 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.315: [egismoc] ENROLL_STATES entering state 12 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.315: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.315: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.315: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.315: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.319: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.319: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.319: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.319: [egismoc] ENROLL_STATES entering state 13 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.319: New fingerprint ID: FP1-00000000-7-00000000-nobody 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.319: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.319: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.319: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.320: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.321: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.321: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.321: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.321: [egismoc] ENROLL_STATES entering state 14 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.321: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.321: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.321: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.321: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.322: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.322: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.322: Task SSM next state callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.322: [egismoc] ENROLL_STATES entering state 15 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.322: Enrollment was successful! 153s (process:4204): libfprint-device-DEBUG: 03:38:20.322: Device reported enroll completion 153s (process:4204): libfprint-device-DEBUG: 03:38:20.322: Device reported finger status change: FP_FINGER_STATUS_NONE 153s (process:4204): libfprint-device-DEBUG: 03:38:20.322: Print for finger FP_FINGER_RIGHT_INDEX enrolled 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.322: [egismoc] ENROLL_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.322: Task SSM done 153s (process:4204): libfprint-device-DEBUG: 03:38:20.322: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 153s (process:4204): libfprint-device-DEBUG: 03:38:20.322: Updated temperature model after 0.13 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.322: List 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.322: [egismoc] LIST_STATES entering state 0 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.322: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.322: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.322: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.323: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.324: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.324: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.324: List callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.324: Device fingerprint 1: FP1-00000000-2-00000000-nobody 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.324: Device fingerprint 2: FP1-00000000-7-00000000-nobody 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.324: Number of currently enrolled fingerprints on the device is 2 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.324: [egismoc] LIST_STATES entering state 1 153s (process:4204): libfprint-device-DEBUG: 03:38:20.324: Device reported listing completion 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.324: [egismoc] LIST_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.324: Task SSM done 153s (process:4204): libfprint-device-DEBUG: 03:38:20.324: Completing action FPI_DEVICE_ACTION_LIST in idle! 153s (process:4204): libfprint-device-DEBUG: 03:38:20.324: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.324: Delete 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.324: [egismoc] DELETE_STATES entering state 0 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.324: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.324: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.324: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.325: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.326: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.326: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.326: List callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.326: Device fingerprint 1: FP1-00000000-2-00000000-nobody 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.326: Device fingerprint 2: FP1-00000000-7-00000000-nobody 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.326: Number of currently enrolled fingerprints on the device is 2 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.326: [egismoc] DELETE_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.326: Get delete command 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.326: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody) 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.326: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.326: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.326: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.326: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.327: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.327: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.327: Delete callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.327: Response prefix valid: yes 153s (process:4204): libfprint-device-DEBUG: 03:38:20.327: Device reported deletion completion 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.327: [egismoc] DELETE_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.327: Task SSM done 153s (process:4204): libfprint-device-DEBUG: 03:38:20.327: Completing action FPI_DEVICE_ACTION_DELETE in idle! 153s (process:4204): libfprint-device-DEBUG: 03:38:20.327: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.327: List 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.327: [egismoc] LIST_STATES entering state 0 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.327: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.327: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.327: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.328: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.328: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.328: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.328: List callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.328: Device fingerprint 1: FP1-00000000-7-00000000-nobody 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.328: Number of currently enrolled fingerprints on the device is 1 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.328: [egismoc] LIST_STATES entering state 1 153s (process:4204): libfprint-device-DEBUG: 03:38:20.328: Device reported listing completion 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.328: [egismoc] LIST_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.328: Task SSM done 153s (process:4204): libfprint-device-DEBUG: 03:38:20.328: Completing action FPI_DEVICE_ACTION_LIST in idle! 153s (process:4204): libfprint-device-DEBUG: 03:38:20.328: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.329: Clear storage 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.329: [egismoc] DELETE_STATES entering state 0 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.329: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.329: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.329: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.329: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.330: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.330: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.330: List callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.330: Device fingerprint 1: FP1-00000000-7-00000000-nobody 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.330: Number of currently enrolled fingerprints on the device is 1 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.330: [egismoc] DELETE_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.330: Get delete command 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.330: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.330: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.330: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.331: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.331: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.331: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.331: Delete callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.331: Response prefix valid: yes 153s (process:4204): libfprint-device-DEBUG: 03:38:20.331: Device reported deletion completion 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.331: [egismoc] DELETE_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.331: Task SSM done 153s (process:4204): libfprint-device-DEBUG: 03:38:20.331: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 153s (process:4204): libfprint-device-DEBUG: 03:38:20.331: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.331: List 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.331: [egismoc] LIST_STATES entering state 0 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.331: Execute command and get response 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.331: Get check bytes 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.331: [egismoc] CMD_STATES entering state 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.332: [egismoc] CMD_STATES entering state 1 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.333: Command receive callback 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.333: [egismoc] CMD_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.333: List callback 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.333: Number of currently enrolled fingerprints on the device is 0 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.333: [egismoc] LIST_STATES entering state 1 153s (process:4204): libfprint-device-DEBUG: 03:38:20.333: Device reported listing completion 153s (process:4204): libfprint-SSM-DEBUG: 03:38:20.333: [egismoc] LIST_STATES completed successfully 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.333: Task SSM done 153s (process:4204): libfprint-device-DEBUG: 03:38:20.333: Completing action FPI_DEVICE_ACTION_LIST in idle! 153s (process:4204): libfprint-device-DEBUG: 03:38:20.333: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.333: Closing device 153s (process:4204): libfprint-egismoc-DEBUG: 03:38:20.333: Cancel 153s (process:4204): libfprint-device-DEBUG: 03:38:20.333: Device reported close completion 153s (process:4204): libfprint-device-DEBUG: 03:38:20.333: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 153s (process:4204): libfprint-device-DEBUG: 03:38:20.334: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 153s 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 7, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 8, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 8, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 9, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 10, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 11, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 12, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 13, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 14, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 15, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 16, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 17, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 18, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 19, , None, None) 153s finger status: 153s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7d9ac322e740 (FpiDeviceEgisMoc at 0x4b104030)>, 20, , None, None) 153s enroll new finger done 153s listing - device should have 2 prints 153s deleting first print 153s delete done 153s listing - device should only have second print 153s clear device storage 153s clear done 153s listing - device should be empty 153s ** (umockdev-run:4200): DEBUG: 03:38:20.346: umockdev.vala:154: Removing test bed /tmp/umockdev.RW8G22 153s (umockdev-run:4200): GLib-DEBUG: 03:38:20.352: unsetenv() is not thread-safe and should not be used after threads are created 153s PASS: libfprint-2/driver-egismoc-0587.test 153s Running test: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_current.test 153s TAP version 14 153s # random seed: R02Sdf539b32441e512dff0bad754442c284 153s 1..14 153s # Start of device tests 153s # Start of async tests 153s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 153s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 153s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7bfd448835d0, GType is 21125044139824 153s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 153s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 153s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 153s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 153s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 153s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 153s # libfprint-context-DEBUG: created 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 153s # 153s # libfprint-device-DEBUG: Device reported probe completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 153s # 153s # libfprint-device-DEBUG: Device reported open completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 153s # 153s # libfprint-device-DEBUG: Device reported close completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s ok 1 /device/async/open 153s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 153s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 153s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7bfd448835d0, GType is 21125044139824 153s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 153s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 153s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 153s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 153s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 153s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 153s # libfprint-context-DEBUG: created 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 153s # 153s # libfprint-device-DEBUG: Device reported probe completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 153s # 153s # libfprint-device-DEBUG: Device reported open completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 153s # 153s # libfprint-device-DEBUG: Device reported close completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s ok 2 /device/async/close 153s # End of async tests 153s # Start of sync tests 153s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 153s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 153s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7bfd448835d0, GType is 21125044139824 153s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 153s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 153s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 153s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 153s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 153s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 153s # libfprint-context-DEBUG: created 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 153s # 153s # libfprint-device-DEBUG: Device reported probe completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 153s # 153s # libfprint-device-DEBUG: Device reported open completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 153s # 153s # libfprint-device-DEBUG: Device reported close completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s ok 3 /device/sync/open 153s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 153s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 153s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7bfd448835d0, GType is 21125044139824 153s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 153s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 153s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 153s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 153s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 153s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 153s # libfprint-context-DEBUG: created 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 153s # 153s # libfprint-device-DEBUG: Device reported probe completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 153s # 153s # libfprint-device-DEBUG: Device reported open completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 153s # 153s # libfprint-device-DEBUG: Device reported close completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s ok 4 /device/sync/close 153s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 153s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 153s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7bfd448835d0, GType is 21125044139824 153s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 153s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 153s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 153s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 153s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 153s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 153s # libfprint-context-DEBUG: created 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 153s # 153s # libfprint-device-DEBUG: Device reported probe completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 153s # 153s # libfprint-device-DEBUG: Device reported open completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 153s # 153s # libfprint-device-DEBUG: Device reported close completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s ok 5 /device/sync/get_driver 153s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 153s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 153s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7bfd448835d0, GType is 21125044139824 153s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 153s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 153s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 153s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 153s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 153s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 153s # libfprint-context-DEBUG: created 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 153s # 153s # libfprint-device-DEBUG: Device reported probe completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 153s # 153s # libfprint-device-DEBUG: Device reported open completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 153s # 153s # libfprint-device-DEBUG: Device reported close completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s ok 6 /device/sync/get_device_id 153s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 153s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 153s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7bfd448835d0, GType is 21125044139824 153s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 153s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 153s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 153s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 153s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 153s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 153s # libfprint-context-DEBUG: created 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 153s # 153s # libfprint-device-DEBUG: Device reported probe completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 153s # 153s # libfprint-device-DEBUG: Device reported open completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 153s # 153s # libfprint-device-DEBUG: Device reported close completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s ok 7 /device/sync/get_name 153s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 153s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 153s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7bfd448835d0, GType is 21125044139824 153s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 153s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 153s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 153s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 153s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 153s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 153s # libfprint-context-DEBUG: created 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 153s # 153s # libfprint-device-DEBUG: Device reported probe completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 153s # 153s # libfprint-device-DEBUG: Device reported open completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 153s # 153s # libfprint-device-DEBUG: Device reported close completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s ok 8 /device/sync/get_scan_type 153s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 153s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 153s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7bfd448835d0, GType is 21125044139824 153s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 153s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 153s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 153s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 153s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 153s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 153s # libfprint-context-DEBUG: created 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 153s # 153s # libfprint-device-DEBUG: Device reported probe completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 153s # 153s # libfprint-device-DEBUG: Device reported open completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 153s # 153s # libfprint-device-DEBUG: Device reported close completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s ok 9 /device/sync/get_nr_enroll_stages 153s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 153s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 153s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7bfd448835d0, GType is 21125044139824 153s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 153s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 153s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 153s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 153s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 153s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 153s # libfprint-context-DEBUG: created 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 153s # 153s # libfprint-device-DEBUG: Device reported probe completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 153s # 153s # libfprint-device-DEBUG: Device reported open completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 153s # 153s # libfprint-device-DEBUG: Device reported close completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s ok 10 /device/sync/supports_identify 153s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 153s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 153s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7bfd448835d0, GType is 21125044139824 153s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 153s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 153s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 153s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 153s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 153s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 153s # libfprint-context-DEBUG: created 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 153s # 153s # libfprint-device-DEBUG: Device reported probe completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 153s # 153s # libfprint-device-DEBUG: Device reported open completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 153s # 153s # libfprint-device-DEBUG: Device reported close completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s ok 11 /device/sync/supports_capture 153s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 153s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 153s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7bfd448835d0, GType is 21125044139824 153s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 153s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 153s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 153s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 153s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 153s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 153s # libfprint-context-DEBUG: created 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 153s # 153s # libfprint-device-DEBUG: Device reported probe completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 153s # 153s # libfprint-device-DEBUG: Device reported open completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 153s # 153s # libfprint-device-DEBUG: Device reported close completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s ok 12 /device/sync/has_storage 153s # Start of open tests 153s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 153s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 153s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7bfd448835d0, GType is 21125044139824 153s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 153s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 153s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 153s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 153s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 153s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 153s # libfprint-context-DEBUG: created 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 153s # 153s # libfprint-device-DEBUG: Device reported probe completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 153s # 153s # libfprint-device-DEBUG: Device reported open completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 153s # 153s # libfprint-device-DEBUG: Device reported close completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s ok 13 /device/sync/open/notify 153s # End of open tests 153s # Start of close tests 153s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 153s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 153s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7bfd448835d0, GType is 21125044139824 153s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 153s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 153s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 153s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 153s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 153s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 153s # libfprint-context-DEBUG: created 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 153s # 153s # libfprint-device-DEBUG: Device reported probe completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 153s # 153s # libfprint-device-DEBUG: Device reported open completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 153s # 153s # libfprint-device-DEBUG: Device reported close completion 153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s ok 14 /device/sync/close/notify 153s # End of close tests 153s # End of sync tests 153s # End of device tests 153s PASS: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_current.test 153s Running test: libfprint-2/virtual-image.test 153s (process:4242): libfprint-context-DEBUG: 03:38:20.553: Initializing FpContext (libfprint version 1.94.8+tod1) 153s (process:4242): libfprint-tod-DEBUG: 03:38:20.553: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 153s (process:4242): libfprint-context-DEBUG: 03:38:20.556: No driver found for USB device 1D6B:0003 153s (process:4242): libfprint-context-DEBUG: 03:38:20.556: No driver found for USB device 0627:0001 153s (process:4242): libfprint-context-DEBUG: 03:38:20.556: No driver found for USB device 0627:0001 153s (process:4242): libfprint-context-DEBUG: 03:38:20.556: No driver found for USB device 1D6B:0002 153s (process:4242): libfprint-context-DEBUG: 03:38:20.556: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-wdudmzz7/virtual-image.socket 153s (process:4242): libfprint-context-DEBUG: 03:38:20.556: created 153s (process:4242): libfprint-device-DEBUG: 03:38:20.558: Device reported probe completion 153s (process:4242): libfprint-device-DEBUG: 03:38:20.558: Completing action FPI_DEVICE_ACTION_PROBE in idle! 153s (process:4242): libfprint-device-DEBUG: 03:38:20.558: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s test_capture_prevents_close (__main__.VirtualImage.test_capture_prevents_close) ... (process:4242): libfprint-virtual_image-DEBUG: 03:38:20.563: 100371420: ../libfprint/drivers/virtual-image.c:216 153s (process:4242): libfprint-virtual_device_connection-DEBUG: 03:38:20.563: 100371499: ../libfprint/drivers/virtual-device-listener.c:153 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.664: Image device open completed 153s (process:4242): libfprint-device-DEBUG: 03:38:20.664: Device reported open completion 153s (process:4242): libfprint-device-DEBUG: 03:38:20.664: Completing action FPI_DEVICE_ACTION_OPEN in idle! 153s (process:4242): libfprint-device-DEBUG: 03:38:20.664: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s (process:4242): libfprint-device-DEBUG: 03:38:20.665: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.665: Activating image device 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.665: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.665: Image device activation completed 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.665: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.665: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 153s (process:4242): libfprint-device-DEBUG: 03:38:20.665: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4242): libfprint-virtual_device_connection-DEBUG: 03:38:20.665: Got a new connection! 153s (process:4242): libfprint-device-DEBUG: 03:38:20.666: Idle cancelling on ongoing operation! 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.666: Deactivating image device 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.666: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.666: Image device deactivation completed 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.666: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 153s (process:4242): libfprint-device-DEBUG: 03:38:20.666: Device reported generic error (Operation was cancelled) during action; action was: FPI_DEVICE_ACTION_CAPTURE 153s (process:4242): libfprint-device-DEBUG: 03:38:20.666: Device reported capture completion 153s (process:4242): libfprint-device-DEBUG: 03:38:20.666: Device reported finger status change: FP_FINGER_STATUS_NONE 153s (process:4242): libfprint-device-DEBUG: 03:38:20.666: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 153s (process:4242): libfprint-device-DEBUG: 03:38:20.666: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s (process:4242): libfprint-virtual_image-DEBUG: 03:38:20.666: 100474552: ../libfprint/drivers/virtual-image.c:244 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.767: Image device close completed 153s (process:4242): libfprint-device-DEBUG: 03:38:20.767: Device reported close completion 153s (process:4242): libfprint-device-DEBUG: 03:38:20.767: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 153s (process:4242): libfprint-device-DEBUG: 03:38:20.767: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s Capture operation finished 153s Capture cancelled as expected 153s ok 153s test_enroll_verify (__main__.VirtualImage.test_enroll_verify) ... (process:4242): libfprint-virtual_image-DEBUG: 03:38:20.767: 100575287: ../libfprint/drivers/virtual-image.c:216 153s (process:4242): libfprint-virtual_device_connection-DEBUG: 03:38:20.767: 100575300: ../libfprint/drivers/virtual-device-listener.c:153 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.867: Image device open completed 153s (process:4242): libfprint-device-DEBUG: 03:38:20.867: Device reported open completion 153s (process:4242): libfprint-device-DEBUG: 03:38:20.867: Completing action FPI_DEVICE_ACTION_OPEN in idle! 153s (process:4242): libfprint-device-DEBUG: 03:38:20.867: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s (process:4242): libfprint-device-DEBUG: 03:38:20.869: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.869: Activating image device 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.869: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.869: Image device activation completed 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.869: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.869: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 153s (process:4242): libfprint-device-DEBUG: 03:38:20.869: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4242): libfprint-virtual_device_connection-DEBUG: 03:38:20.869: Got a new connection! 153s (process:4242): libfprint-virtual_image-DEBUG: 03:38:20.869: image data: 0x4df22100 153s (process:4242): libfprint-device-DEBUG: 03:38:20.869: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.869: Image device reported finger status: on 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.869: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.869: Image device captured an image 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.869: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 153s (process:4242): libfprint-device-DEBUG: 03:38:20.869: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4242): libfprint-device-DEBUG: 03:38:20.869: Device reported finger status change: FP_FINGER_STATUS_NONE 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.869: Image device reported finger status: off 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.869: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 153s (process:4242): libfprint-image-DEBUG: 03:38:20.898: Minutiae scan completed in 0.028232 secs 153s (process:4242): libfprint-device-DEBUG: 03:38:20.898: Device reported enroll progress, reported 1 of 5 have been completed 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.898: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 153s (process:4242): libfprint-device-DEBUG: 03:38:20.898: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4242): libfprint-device-DEBUG: 03:38:20.898: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.898: Image device reported finger status: on 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.898: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 153s (process:4242): libfprint-virtual_image-DEBUG: 03:38:20.898: image data: 0x4df22100 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.899: Image device captured an image 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.899: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 153s (process:4242): libfprint-device-DEBUG: 03:38:20.899: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4242): libfprint-image-DEBUG: 03:38:20.934: Minutiae scan completed in 0.035519 secs 153s (process:4242): libfprint-device-DEBUG: 03:38:20.935: Device reported enroll progress, reported 2 of 5 have been completed 153s (process:4242): libfprint-device-DEBUG: 03:38:20.935: Device reported finger status change: FP_FINGER_STATUS_NONE 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.935: Image device reported finger status: off 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.935: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.935: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 153s (process:4242): libfprint-device-DEBUG: 03:38:20.935: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4242): libfprint-virtual_image-DEBUG: 03:38:20.935: image data: 0x4df22100 153s (process:4242): libfprint-device-DEBUG: 03:38:20.935: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.935: Image device reported finger status: on 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.935: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.935: Image device captured an image 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.935: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 153s (process:4242): libfprint-device-DEBUG: 03:38:20.935: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4242): libfprint-device-DEBUG: 03:38:20.935: Device reported finger status change: FP_FINGER_STATUS_NONE 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.935: Image device reported finger status: off 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.935: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 153s (process:4242): libfprint-image-DEBUG: 03:38:20.964: Minutiae scan completed in 0.028693 secs 153s (process:4242): libfprint-device-DEBUG: 03:38:20.964: Device reported enroll progress, reported 3 of 5 have been completed 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.964: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 153s (process:4242): libfprint-device-DEBUG: 03:38:20.964: Device reported finger status change: FP_FINGER_STATUS_NEEDED 153s (process:4242): libfprint-virtual_image-DEBUG: 03:38:20.964: image data: 0x4df22100 153s (process:4242): libfprint-device-DEBUG: 03:38:20.964: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.964: Image device reported finger status: on 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.964: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.964: Image device captured an image 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.964: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 153s (process:4242): libfprint-device-DEBUG: 03:38:20.964: Device reported finger status change: FP_FINGER_STATUS_PRESENT 153s (process:4242): libfprint-device-DEBUG: 03:38:20.964: Device reported finger status change: FP_FINGER_STATUS_NONE 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.964: Image device reported finger status: off 153s (process:4242): libfprint-image_device-DEBUG: 03:38:20.964: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 154s (process:4242): libfprint-image-DEBUG: 03:38:20.992: Minutiae scan completed in 0.027683 secs 154s (process:4242): libfprint-device-DEBUG: 03:38:20.993: Device reported enroll progress, reported 4 of 5 have been completed 154s (process:4242): libfprint-image_device-DEBUG: 03:38:20.993: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 154s (process:4242): libfprint-device-DEBUG: 03:38:20.993: Device reported finger status change: FP_FINGER_STATUS_NEEDED 154s (process:4242): libfprint-virtual_image-DEBUG: 03:38:20.993: image data: 0x4df22100 154s (process:4242): libfprint-device-DEBUG: 03:38:20.993: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 154s (process:4242): libfprint-image_device-DEBUG: 03:38:20.993: Image device reported finger status: on 154s (process:4242): libfprint-image_device-DEBUG: 03:38:20.993: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 154s (process:4242): libfprint-image_device-DEBUG: 03:38:20.993: Image device captured an image 154s (process:4242): libfprint-image_device-DEBUG: 03:38:20.993: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 154s (process:4242): libfprint-device-DEBUG: 03:38:20.993: Device reported finger status change: FP_FINGER_STATUS_PRESENT 154s (process:4242): libfprint-device-DEBUG: 03:38:20.993: Device reported finger status change: FP_FINGER_STATUS_NONE 154s (process:4242): libfprint-image_device-DEBUG: 03:38:20.993: Image device reported finger status: off 154s (process:4242): libfprint-image_device-DEBUG: 03:38:20.993: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 154s (process:4242): libfprint-device-DEBUG: 03:38:21.004: Updated temperature model after 0.14 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s (process:4242): libfprint-image-DEBUG: 03:38:21.021: Minutiae scan completed in 0.027749 secs 154s (process:4242): libfprint-device-DEBUG: 03:38:21.021: Device reported enroll progress, reported 5 of 5 have been completed 154s (process:4242): libfprint-image_device-DEBUG: 03:38:21.021: Deactivating image device 154s (process:4242): libfprint-image_device-DEBUG: 03:38:21.021: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 154s (process:4242): libfprint-image_device-DEBUG: 03:38:21.021: Image device deactivation completed 154s (process:4242): libfprint-image_device-DEBUG: 03:38:21.021: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 154s (process:4242): libfprint-device-DEBUG: 03:38:21.021: Device reported enroll completion 154s (process:4242): libfprint-device-DEBUG: 03:38:21.021: Print for finger FP_FINGER_LEFT_THUMB enrolled 154s (process:4242): libfprint-device-DEBUG: 03:38:21.022: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 154s (process:4242): libfprint-device-DEBUG: 03:38:21.022: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s (process:4242): libfprint-device-DEBUG: 03:38:21.022: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s (process:4242): libfprint-image_device-DEBUG: 03:38:21.022: Activating image device 154s (process:4242): libfprint-image_device-DEBUG: 03:38:21.022: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 154s (process:4242): libfprint-image_device-DEBUG: 03:38:21.022: Image device activation completed 154s (process:4242): libfprint-image_device-DEBUG: 03:38:21.022: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 154s (process:4242): libfprint-image_device-DEBUG: 03:38:21.022: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 154s (process:4242): libfprint-device-DEBUG: 03:38:21.022: Device reported finger status change: FP_FINGER_STATUS_NEEDED 154s (process:4242): libfprint-virtual_image-DEBUG: 03:38:21.022: image data: 0x4df22100 154s (process:4242): libfprint-device-DEBUG: 03:38:21.022: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 154s (process:4242): libfprint-image_device-DEBUG: 03:38:21.022: Image device reported finger status: on 154s (process:4242): libfprint-image_device-DEBUG: 03:38:21.022: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 154s (process:4242): libfprint-image_device-DEBUG: 03:38:21.022: Image device captured an image 154s (process:4242): libfprint-image_device-DEBUG: 03:38:21.022: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 154s (process:4242): libfprint-device-DEBUG: 03:38:21.022: Device reported finger status change: FP_FINGER_STATUS_PRESENT 154s (process:4242): libfprint-device-DEBUG: 03:38:21.022: Device reported finger status change: FP_FINGER_STATUS_NONE 154s (process:4242): libfprint-image_device-DEBUG: 03:38:21.022: Image device reported finger status: off 154s (process:4242): libfprint-image_device-DEBUG: 03:38:21.022: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 154s (process:4242): libfprint-image_device-DEBUG: 03:38:21.022: Deactivating image device 154s (process:4242): libfprint-image_device-DEBUG: 03:38:21.022: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 154s (process:4242): libfprint-image_device-DEBUG: 03:38:21.022: Image device deactivation completed 154s (process:4242): libfprint-image_device-DEBUG: 03:38:21.022: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 154s (process:4242): libfprint-image-DEBUG: 03:38:21.050: Minutiae scan completed in 0.027551 secs 154s Executing: libfprint-2/virtual-image.test 155s (process:4242): libfprint-print-DEBUG: 03:38:22.108: score 1093/40 155s (process:4242): libfprint-device-DEBUG: 03:38:22.108: Device reported verify result 155s (process:4242): libfprint-device-DEBUG: 03:38:22.109: Device reported verify completion 155s (process:4242): libfprint-device-DEBUG: 03:38:22.109: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 155s (process:4242): libfprint-device-DEBUG: 03:38:22.109: Updated temperature model after 1.09 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 155s (process:4242): libfprint-device-DEBUG: 03:38:22.109: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.109: Activating image device 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.109: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.109: Image device activation completed 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.110: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.110: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 155s (process:4242): libfprint-device-DEBUG: 03:38:22.110: Device reported finger status change: FP_FINGER_STATUS_NEEDED 155s (process:4242): libfprint-virtual_image-DEBUG: 03:38:22.110: image data: 0x4df782a0 155s (process:4242): libfprint-device-DEBUG: 03:38:22.110: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.110: Image device reported finger status: on 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.110: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.110: Image device captured an image 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.110: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 155s (process:4242): libfprint-device-DEBUG: 03:38:22.110: Device reported finger status change: FP_FINGER_STATUS_PRESENT 155s (process:4242): libfprint-device-DEBUG: 03:38:22.110: Device reported finger status change: FP_FINGER_STATUS_NONE 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.110: Image device reported finger status: off 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.110: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.110: Deactivating image device 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.110: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.110: Image device deactivation completed 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.110: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 155s (process:4242): libfprint-image-DEBUG: 03:38:22.136: Minutiae scan completed in 0.025779 secs 155s (process:4242): libfprint-print-DEBUG: 03:38:22.144: score 10/40 155s (process:4242): libfprint-print-DEBUG: 03:38:22.151: score 10/40 155s (process:4242): libfprint-print-DEBUG: 03:38:22.158: score 10/40 155s (process:4242): libfprint-print-DEBUG: 03:38:22.165: score 10/40 155s (process:4242): libfprint-print-DEBUG: 03:38:22.172: score 10/40 155s (process:4242): libfprint-device-DEBUG: 03:38:22.172: Device reported verify result 155s (process:4242): libfprint-device-DEBUG: 03:38:22.172: Device reported verify completion 155s (process:4242): libfprint-device-DEBUG: 03:38:22.173: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 155s (process:4242): libfprint-device-DEBUG: 03:38:22.173: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 155s (process:4242): libfprint-device-DEBUG: 03:38:22.173: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.173: Activating image device 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.173: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.173: Image device activation completed 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.173: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.173: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 155s (process:4242): libfprint-device-DEBUG: 03:38:22.173: Device reported finger status change: FP_FINGER_STATUS_NEEDED 155s (process:4242): libfprint-virtual_image-DEBUG: 03:38:22.174: image data: 0x4df872b0 155s (process:4242): libfprint-device-DEBUG: 03:38:22.174: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.174: Image device reported finger status: on 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.174: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.174: Image device captured an image 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.174: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 155s (process:4242): libfprint-device-DEBUG: 03:38:22.174: Device reported finger status change: FP_FINGER_STATUS_PRESENT 155s (process:4242): libfprint-device-DEBUG: 03:38:22.174: Device reported finger status change: FP_FINGER_STATUS_NONE 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.174: Image device reported finger status: off 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.174: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 155s (process:4242): libfprint-image-DEBUG: 03:38:22.199: Minutiae scan completed in 0.024739 secs 155s (process:4242): libfprint-device-DEBUG: 03:38:22.199: Device reported enroll progress, reported 1 of 5 have been completed 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.199: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 155s (process:4242): libfprint-device-DEBUG: 03:38:22.199: Device reported finger status change: FP_FINGER_STATUS_NEEDED 155s (process:4242): libfprint-device-DEBUG: 03:38:22.199: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.199: Image device reported finger status: on 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.199: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 155s (process:4242): libfprint-virtual_image-DEBUG: 03:38:22.199: image data: 0x4df872b0 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.199: Image device captured an image 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.199: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 155s (process:4242): libfprint-device-DEBUG: 03:38:22.199: Device reported finger status change: FP_FINGER_STATUS_PRESENT 155s (process:4242): libfprint-image-DEBUG: 03:38:22.224: Minutiae scan completed in 0.024434 secs 155s (process:4242): libfprint-device-DEBUG: 03:38:22.224: Device reported enroll progress, reported 2 of 5 have been completed 155s (process:4242): libfprint-device-DEBUG: 03:38:22.224: Device reported finger status change: FP_FINGER_STATUS_NONE 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.224: Image device reported finger status: off 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.224: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.224: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 155s (process:4242): libfprint-device-DEBUG: 03:38:22.224: Device reported finger status change: FP_FINGER_STATUS_NEEDED 155s (process:4242): libfprint-virtual_image-DEBUG: 03:38:22.224: image data: 0x4df872b0 155s (process:4242): libfprint-device-DEBUG: 03:38:22.224: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.224: Image device reported finger status: on 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.224: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.224: Image device captured an image 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.224: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 155s (process:4242): libfprint-device-DEBUG: 03:38:22.224: Device reported finger status change: FP_FINGER_STATUS_PRESENT 155s (process:4242): libfprint-device-DEBUG: 03:38:22.224: Device reported finger status change: FP_FINGER_STATUS_NONE 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.224: Image device reported finger status: off 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.224: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 155s (process:4242): libfprint-image-DEBUG: 03:38:22.249: Minutiae scan completed in 0.024672 secs 155s (process:4242): libfprint-device-DEBUG: 03:38:22.249: Device reported enroll progress, reported 3 of 5 have been completed 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.249: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 155s (process:4242): libfprint-device-DEBUG: 03:38:22.249: Device reported finger status change: FP_FINGER_STATUS_NEEDED 155s (process:4242): libfprint-virtual_image-DEBUG: 03:38:22.249: image data: 0x4df872b0 155s (process:4242): libfprint-device-DEBUG: 03:38:22.249: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.250: Image device reported finger status: on 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.250: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.250: Image device captured an image 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.250: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 155s (process:4242): libfprint-device-DEBUG: 03:38:22.250: Device reported finger status change: FP_FINGER_STATUS_PRESENT 155s (process:4242): libfprint-device-DEBUG: 03:38:22.250: Device reported finger status change: FP_FINGER_STATUS_NONE 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.250: Image device reported finger status: off 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.250: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 155s (process:4242): libfprint-image-DEBUG: 03:38:22.274: Minutiae scan completed in 0.024606 secs 155s (process:4242): libfprint-device-DEBUG: 03:38:22.274: Device reported enroll progress, reported 4 of 5 have been completed 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.275: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 155s (process:4242): libfprint-device-DEBUG: 03:38:22.275: Device reported finger status change: FP_FINGER_STATUS_NEEDED 155s (process:4242): libfprint-virtual_image-DEBUG: 03:38:22.275: image data: 0x4df872b0 155s (process:4242): libfprint-device-DEBUG: 03:38:22.275: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.275: Image device reported finger status: on 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.275: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.275: Image device captured an image 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.275: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 155s (process:4242): libfprint-device-DEBUG: 03:38:22.275: Device reported finger status change: FP_FINGER_STATUS_PRESENT 155s (process:4242): libfprint-device-DEBUG: 03:38:22.275: Device reported finger status change: FP_FINGER_STATUS_NONE 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.275: Image device reported finger status: off 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.275: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 155s (process:4242): libfprint-image-DEBUG: 03:38:22.299: Minutiae scan completed in 0.024475 secs 155s (process:4242): libfprint-device-DEBUG: 03:38:22.300: Device reported enroll progress, reported 5 of 5 have been completed 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.300: Deactivating image device 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.300: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.300: Image device deactivation completed 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.300: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 155s (process:4242): libfprint-device-DEBUG: 03:38:22.300: Device reported enroll completion 155s (process:4242): libfprint-device-DEBUG: 03:38:22.300: Print for finger FP_FINGER_LEFT_THUMB enrolled 155s (process:4242): libfprint-device-DEBUG: 03:38:22.300: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 155s (process:4242): libfprint-device-DEBUG: 03:38:22.300: Updated temperature model after 0.13 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 155s (process:4242): libfprint-device-DEBUG: 03:38:22.300: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.300: Activating image device 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.300: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.300: Image device activation completed 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.300: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.300: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 155s (process:4242): libfprint-device-DEBUG: 03:38:22.300: Device reported finger status change: FP_FINGER_STATUS_NEEDED 155s (process:4242): libfprint-virtual_image-DEBUG: 03:38:22.300: image data: 0x4df69260 155s (process:4242): libfprint-device-DEBUG: 03:38:22.300: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.300: Image device reported finger status: on 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.300: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.300: Image device captured an image 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.300: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 155s (process:4242): libfprint-device-DEBUG: 03:38:22.300: Device reported finger status change: FP_FINGER_STATUS_PRESENT 155s (process:4242): libfprint-device-DEBUG: 03:38:22.300: Device reported finger status change: FP_FINGER_STATUS_NONE 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.300: Image device reported finger status: off 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.300: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.300: Deactivating image device 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.300: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.300: Image device deactivation completed 155s (process:4242): libfprint-image_device-DEBUG: 03:38:22.300: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 155s (process:4242): libfprint-image-DEBUG: 03:38:22.328: Minutiae scan completed in 0.027752 secs 156s (process:4242): libfprint-print-DEBUG: 03:38:23.391: score 1093/40 156s (process:4242): libfprint-device-DEBUG: 03:38:23.392: Device reported verify result 156s (process:4242): libfprint-device-DEBUG: 03:38:23.392: Device reported verify completion 156s (process:4242): libfprint-device-DEBUG: 03:38:23.392: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 156s (process:4242): libfprint-device-DEBUG: 03:38:23.392: Updated temperature model after 1.09 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 156s (process:4242): libfprint-device-DEBUG: 03:38:23.392: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.392: Activating image device 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.392: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.392: Image device activation completed 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.392: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.392: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 156s (process:4242): libfprint-device-DEBUG: 03:38:23.392: Device reported finger status change: FP_FINGER_STATUS_NEEDED 156s (process:4242): libfprint-virtual_image-DEBUG: 03:38:23.392: image data: 0x4df782a0 156s (process:4242): libfprint-device-DEBUG: 03:38:23.392: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.392: Image device reported finger status: on 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.392: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.392: Image device captured an image 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.396: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 156s (process:4242): libfprint-device-DEBUG: 03:38:23.396: Device reported finger status change: FP_FINGER_STATUS_PRESENT 156s (process:4242): libfprint-device-DEBUG: 03:38:23.396: Device reported finger status change: FP_FINGER_STATUS_NONE 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.396: Image device reported finger status: off 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.396: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.396: Deactivating image device 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.396: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.396: Image device deactivation completed 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.396: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 156s (process:4242): libfprint-image-DEBUG: 03:38:23.416: Minutiae scan completed in 0.024068 secs 156s (process:4242): libfprint-print-DEBUG: 03:38:23.424: score 10/40 156s (process:4242): libfprint-print-DEBUG: 03:38:23.431: score 10/40 156s (process:4242): libfprint-print-DEBUG: 03:38:23.438: score 10/40 156s (process:4242): libfprint-print-DEBUG: 03:38:23.444: score 10/40 156s (process:4242): libfprint-print-DEBUG: 03:38:23.451: score 10/40 156s (process:4242): libfprint-print-DEBUG: 03:38:23.663: score 855/40 156s (process:4242): libfprint-device-DEBUG: 03:38:23.663: Device reported verify result 156s (process:4242): libfprint-device-DEBUG: 03:38:23.663: Device reported verify completion 156s (process:4242): libfprint-device-DEBUG: 03:38:23.663: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 156s (process:4242): libfprint-device-DEBUG: 03:38:23.663: Updated temperature model after 0.27 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 156s (process:4242): libfprint-device-DEBUG: 03:38:23.663: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.663: Activating image device 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.663: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.664: Image device activation completed 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.664: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.664: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 156s (process:4242): libfprint-device-DEBUG: 03:38:23.664: Device reported finger status change: FP_FINGER_STATUS_NEEDED 156s (process:4242): libfprint-device-DEBUG: 03:38:23.664: Device reported verify result 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.664: Deactivating image device 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.664: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.664: Image device deactivation completed 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.664: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 156s (process:4242): libfprint-device-DEBUG: 03:38:23.664: Device reported verify completion 156s (process:4242): libfprint-device-DEBUG: 03:38:23.664: Device reported finger status change: FP_FINGER_STATUS_NONE 156s (process:4242): libfprint-device-DEBUG: 03:38:23.664: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 156s (process:4242): libfprint-device-DEBUG: 03:38:23.664: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 156s (process:4242): libfprint-device-DEBUG: 03:38:23.664: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.664: Activating image device 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.664: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.664: Image device activation completed 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.664: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.664: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 156s (process:4242): libfprint-device-DEBUG: 03:38:23.664: Device reported finger status change: FP_FINGER_STATUS_NEEDED 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.664: Deactivating image device 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.664: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.664: Image device deactivation completed 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.664: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 156s (process:4242): libfprint-device-DEBUG: 03:38:23.664: Device reported generic error (An unspecified error occurred!) during action; action was: FPI_DEVICE_ACTION_VERIFY 156s (process:4242): libfprint-device-DEBUG: 03:38:23.664: Device reported verify completion 156s (process:4242): libfprint-device-DEBUG: 03:38:23.664: Device reported finger status change: FP_FINGER_STATUS_NONE 156s (process:4242): libfprint-device-DEBUG: 03:38:23.664: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 156s (process:4242): libfprint-device-DEBUG: 03:38:23.665: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 156s (process:4242): libfprint-virtual_image-DEBUG: 03:38:23.665: 103472751: ../libfprint/drivers/virtual-image.c:244 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.765: Image device close completed 156s (process:4242): libfprint-device-DEBUG: 03:38:23.765: Device reported close completion 156s (process:4242): libfprint-device-DEBUG: 03:38:23.765: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 156s (process:4242): libfprint-device-DEBUG: 03:38:23.765: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 156s Print was processed, continuing 156s Print was processed, continuing 156s Print was processed, continuing 156s Print was processed, continuing 156s Print was processed, continuing 156s Enroll done 156s Print was processed, continuing 156s Print was processed, continuing 156s Print was processed, continuing 156s Print was processed, continuing 156s Print was processed, continuing 156s Enroll done 156s fp - device - error - quark: An unspecified error occurred! (0) 156s ok 156s test_features (__main__.VirtualImage.test_features) ... (process:4242): libfprint-virtual_image-DEBUG: 03:38:23.765: 103573236: ../libfprint/drivers/virtual-image.c:216 156s (process:4242): libfprint-virtual_device_connection-DEBUG: 03:38:23.765: 103573284: ../libfprint/drivers/virtual-device-listener.c:153 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.865: Image device open completed 156s (process:4242): libfprint-device-DEBUG: 03:38:23.865: Device reported open completion 156s (process:4242): libfprint-device-DEBUG: 03:38:23.865: Completing action FPI_DEVICE_ACTION_OPEN in idle! 156s (process:4242): libfprint-device-DEBUG: 03:38:23.865: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 156s (process:4242): libfprint-virtual_image-DEBUG: 03:38:23.865: 103673591: ../libfprint/drivers/virtual-image.c:244 156s (process:4242): libfprint-image_device-DEBUG: 03:38:23.965: Image device close completed 156s (process:4242): libfprint-device-DEBUG: 03:38:23.965: Device reported close completion 156s (process:4242): libfprint-device-DEBUG: 03:38:23.965: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 156s (process:4242): libfprint-device-DEBUG: 03:38:23.966: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 156s ok 156s test_identify (__main__.VirtualImage.test_identify) ... (process:4242): libfprint-virtual_image-DEBUG: 03:38:23.966: 103773849: ../libfprint/drivers/virtual-image.c:216 156s (process:4242): libfprint-virtual_device_connection-DEBUG: 03:38:23.966: 103773874: ../libfprint/drivers/virtual-device-listener.c:153 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.066: Image device open completed 157s (process:4242): libfprint-device-DEBUG: 03:38:24.066: Device reported open completion 157s (process:4242): libfprint-device-DEBUG: 03:38:24.066: Completing action FPI_DEVICE_ACTION_OPEN in idle! 157s (process:4242): libfprint-device-DEBUG: 03:38:24.066: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s (process:4242): libfprint-device-DEBUG: 03:38:24.066: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.066: Activating image device 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.066: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.066: Image device activation completed 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.066: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.066: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 157s (process:4242): libfprint-device-DEBUG: 03:38:24.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED 157s (process:4242): libfprint-virtual_device_connection-DEBUG: 03:38:24.066: Got a new connection! 157s (process:4242): libfprint-virtual_image-DEBUG: 03:38:24.067: image data: 0x4df69260 157s (process:4242): libfprint-device-DEBUG: 03:38:24.067: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.067: Image device reported finger status: on 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.067: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.067: Image device captured an image 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.067: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 157s (process:4242): libfprint-device-DEBUG: 03:38:24.067: Device reported finger status change: FP_FINGER_STATUS_PRESENT 157s (process:4242): libfprint-device-DEBUG: 03:38:24.067: Device reported finger status change: FP_FINGER_STATUS_NONE 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.067: Image device reported finger status: off 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.067: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 157s (process:4242): libfprint-image-DEBUG: 03:38:24.094: Minutiae scan completed in 0.027553 secs 157s (process:4242): libfprint-device-DEBUG: 03:38:24.095: Device reported enroll progress, reported 1 of 5 have been completed 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.095: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 157s (process:4242): libfprint-device-DEBUG: 03:38:24.095: Device reported finger status change: FP_FINGER_STATUS_NEEDED 157s (process:4242): libfprint-device-DEBUG: 03:38:24.095: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.095: Image device reported finger status: on 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.095: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 157s (process:4242): libfprint-virtual_image-DEBUG: 03:38:24.095: image data: 0x4df69260 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.095: Image device captured an image 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.095: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 157s (process:4242): libfprint-device-DEBUG: 03:38:24.096: Device reported finger status change: FP_FINGER_STATUS_PRESENT 157s (process:4242): libfprint-image-DEBUG: 03:38:24.123: Minutiae scan completed in 0.027851 secs 157s (process:4242): libfprint-device-DEBUG: 03:38:24.123: Device reported enroll progress, reported 2 of 5 have been completed 157s (process:4242): libfprint-device-DEBUG: 03:38:24.124: Device reported finger status change: FP_FINGER_STATUS_NONE 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.124: Image device reported finger status: off 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.124: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.124: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 157s (process:4242): libfprint-device-DEBUG: 03:38:24.124: Device reported finger status change: FP_FINGER_STATUS_NEEDED 157s (process:4242): libfprint-virtual_image-DEBUG: 03:38:24.124: image data: 0x4df69260 157s (process:4242): libfprint-device-DEBUG: 03:38:24.124: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.124: Image device reported finger status: on 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.124: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.124: Image device captured an image 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.124: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 157s (process:4242): libfprint-device-DEBUG: 03:38:24.124: Device reported finger status change: FP_FINGER_STATUS_PRESENT 157s (process:4242): libfprint-device-DEBUG: 03:38:24.124: Device reported finger status change: FP_FINGER_STATUS_NONE 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.124: Image device reported finger status: off 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.124: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 157s (process:4242): libfprint-image-DEBUG: 03:38:24.152: Minutiae scan completed in 0.027480 secs 157s (process:4242): libfprint-device-DEBUG: 03:38:24.153: Device reported enroll progress, reported 3 of 5 have been completed 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.153: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 157s (process:4242): libfprint-device-DEBUG: 03:38:24.153: Device reported finger status change: FP_FINGER_STATUS_NEEDED 157s (process:4242): libfprint-virtual_image-DEBUG: 03:38:24.153: image data: 0x4df69260 157s (process:4242): libfprint-device-DEBUG: 03:38:24.153: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.153: Image device reported finger status: on 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.153: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.153: Image device captured an image 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.153: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 157s (process:4242): libfprint-device-DEBUG: 03:38:24.153: Device reported finger status change: FP_FINGER_STATUS_PRESENT 157s (process:4242): libfprint-device-DEBUG: 03:38:24.153: Device reported finger status change: FP_FINGER_STATUS_NONE 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.153: Image device reported finger status: off 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.154: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 157s (process:4242): libfprint-image-DEBUG: 03:38:24.181: Minutiae scan completed in 0.027468 secs 157s (process:4242): libfprint-device-DEBUG: 03:38:24.181: Device reported enroll progress, reported 4 of 5 have been completed 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.181: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 157s (process:4242): libfprint-device-DEBUG: 03:38:24.181: Device reported finger status change: FP_FINGER_STATUS_NEEDED 157s (process:4242): libfprint-virtual_image-DEBUG: 03:38:24.181: image data: 0x4df69260 157s (process:4242): libfprint-device-DEBUG: 03:38:24.182: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.182: Image device reported finger status: on 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.182: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.182: Image device captured an image 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.182: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 157s (process:4242): libfprint-device-DEBUG: 03:38:24.182: Device reported finger status change: FP_FINGER_STATUS_PRESENT 157s (process:4242): libfprint-device-DEBUG: 03:38:24.182: Device reported finger status change: FP_FINGER_STATUS_NONE 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.182: Image device reported finger status: off 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.182: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 157s (process:4242): libfprint-image-DEBUG: 03:38:24.209: Minutiae scan completed in 0.027495 secs 157s (process:4242): libfprint-device-DEBUG: 03:38:24.209: Device reported enroll progress, reported 5 of 5 have been completed 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.209: Deactivating image device 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.209: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.209: Image device deactivation completed 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.210: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 157s (process:4242): libfprint-device-DEBUG: 03:38:24.210: Device reported enroll completion 157s (process:4242): libfprint-device-DEBUG: 03:38:24.210: Print for finger FP_FINGER_LEFT_THUMB enrolled 157s (process:4242): libfprint-device-DEBUG: 03:38:24.210: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 157s (process:4242): libfprint-device-DEBUG: 03:38:24.210: Updated temperature model after 0.14 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s (process:4242): libfprint-device-DEBUG: 03:38:24.210: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.210: Activating image device 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.210: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.210: Image device activation completed 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.210: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.210: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 157s (process:4242): libfprint-device-DEBUG: 03:38:24.210: Device reported finger status change: FP_FINGER_STATUS_NEEDED 157s (process:4242): libfprint-virtual_image-DEBUG: 03:38:24.210: image data: 0x4df782a0 157s (process:4242): libfprint-device-DEBUG: 03:38:24.210: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.210: Image device reported finger status: on 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.210: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.210: Image device captured an image 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.210: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 157s (process:4242): libfprint-device-DEBUG: 03:38:24.210: Device reported finger status change: FP_FINGER_STATUS_PRESENT 157s (process:4242): libfprint-device-DEBUG: 03:38:24.210: Device reported finger status change: FP_FINGER_STATUS_NONE 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.210: Image device reported finger status: off 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.210: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 157s (process:4242): libfprint-image-DEBUG: 03:38:24.235: Minutiae scan completed in 0.024468 secs 157s (process:4242): libfprint-device-DEBUG: 03:38:24.235: Device reported enroll progress, reported 1 of 5 have been completed 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.235: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 157s (process:4242): libfprint-device-DEBUG: 03:38:24.235: Device reported finger status change: FP_FINGER_STATUS_NEEDED 157s (process:4242): libfprint-device-DEBUG: 03:38:24.235: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.235: Image device reported finger status: on 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.235: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 157s (process:4242): libfprint-virtual_image-DEBUG: 03:38:24.236: image data: 0x4df782a0 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.236: Image device captured an image 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.236: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 157s (process:4242): libfprint-device-DEBUG: 03:38:24.236: Device reported finger status change: FP_FINGER_STATUS_PRESENT 157s (process:4242): libfprint-image-DEBUG: 03:38:24.260: Minutiae scan completed in 0.024202 secs 157s (process:4242): libfprint-device-DEBUG: 03:38:24.260: Device reported enroll progress, reported 2 of 5 have been completed 157s (process:4242): libfprint-device-DEBUG: 03:38:24.261: Device reported finger status change: FP_FINGER_STATUS_NONE 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.261: Image device reported finger status: off 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.261: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.261: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 157s (process:4242): libfprint-device-DEBUG: 03:38:24.261: Device reported finger status change: FP_FINGER_STATUS_NEEDED 157s (process:4242): libfprint-virtual_image-DEBUG: 03:38:24.261: image data: 0x4df782a0 157s (process:4242): libfprint-device-DEBUG: 03:38:24.261: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.261: Image device reported finger status: on 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.261: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.262: Image device captured an image 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.262: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 157s (process:4242): libfprint-device-DEBUG: 03:38:24.262: Device reported finger status change: FP_FINGER_STATUS_PRESENT 157s (process:4242): libfprint-device-DEBUG: 03:38:24.262: Device reported finger status change: FP_FINGER_STATUS_NONE 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.262: Image device reported finger status: off 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.262: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 157s (process:4242): libfprint-image-DEBUG: 03:38:24.286: Minutiae scan completed in 0.024450 secs 157s (process:4242): libfprint-device-DEBUG: 03:38:24.286: Device reported enroll progress, reported 3 of 5 have been completed 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.286: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 157s (process:4242): libfprint-device-DEBUG: 03:38:24.286: Device reported finger status change: FP_FINGER_STATUS_NEEDED 157s (process:4242): libfprint-virtual_image-DEBUG: 03:38:24.287: image data: 0x4df782a0 157s (process:4242): libfprint-device-DEBUG: 03:38:24.287: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.287: Image device reported finger status: on 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.287: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.287: Image device captured an image 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.287: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 157s (process:4242): libfprint-device-DEBUG: 03:38:24.287: Device reported finger status change: FP_FINGER_STATUS_PRESENT 157s (process:4242): libfprint-device-DEBUG: 03:38:24.287: Device reported finger status change: FP_FINGER_STATUS_NONE 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.287: Image device reported finger status: off 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.287: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 157s (process:4242): libfprint-image-DEBUG: 03:38:24.311: Minutiae scan completed in 0.024060 secs 157s (process:4242): libfprint-device-DEBUG: 03:38:24.311: Device reported enroll progress, reported 4 of 5 have been completed 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.311: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 157s (process:4242): libfprint-device-DEBUG: 03:38:24.311: Device reported finger status change: FP_FINGER_STATUS_NEEDED 157s (process:4242): libfprint-virtual_image-DEBUG: 03:38:24.311: image data: 0x4df782a0 157s (process:4242): libfprint-device-DEBUG: 03:38:24.311: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.311: Image device reported finger status: on 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.311: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.311: Image device captured an image 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.311: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 157s (process:4242): libfprint-device-DEBUG: 03:38:24.311: Device reported finger status change: FP_FINGER_STATUS_PRESENT 157s (process:4242): libfprint-device-DEBUG: 03:38:24.311: Device reported finger status change: FP_FINGER_STATUS_NONE 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.311: Image device reported finger status: off 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.312: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 157s (process:4242): libfprint-image-DEBUG: 03:38:24.337: Minutiae scan completed in 0.025716 secs 157s (process:4242): libfprint-device-DEBUG: 03:38:24.338: Device reported enroll progress, reported 5 of 5 have been completed 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.338: Deactivating image device 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.338: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.338: Image device deactivation completed 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.338: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 157s (process:4242): libfprint-device-DEBUG: 03:38:24.338: Device reported enroll completion 157s (process:4242): libfprint-device-DEBUG: 03:38:24.338: Print for finger FP_FINGER_LEFT_THUMB enrolled 157s (process:4242): libfprint-device-DEBUG: 03:38:24.338: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 157s (process:4242): libfprint-device-DEBUG: 03:38:24.339: Updated temperature model after 0.13 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s (process:4242): libfprint-device-DEBUG: 03:38:24.339: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.339: Activating image device 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.339: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.339: Image device activation completed 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.339: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.339: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 157s (process:4242): libfprint-device-DEBUG: 03:38:24.339: Device reported finger status change: FP_FINGER_STATUS_NEEDED 157s (process:4242): libfprint-virtual_image-DEBUG: 03:38:24.339: image data: 0x4df782a0 157s (process:4242): libfprint-device-DEBUG: 03:38:24.339: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.339: Image device reported finger status: on 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.339: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.339: Image device captured an image 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.339: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 157s (process:4242): libfprint-device-DEBUG: 03:38:24.339: Device reported finger status change: FP_FINGER_STATUS_PRESENT 157s (process:4242): libfprint-device-DEBUG: 03:38:24.339: Device reported finger status change: FP_FINGER_STATUS_NONE 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.339: Image device reported finger status: off 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.339: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.339: Deactivating image device 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.340: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.340: Image device deactivation completed 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.340: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 157s (process:4242): libfprint-image-DEBUG: 03:38:24.365: Minutiae scan completed in 0.025155 secs 157s (process:4242): libfprint-print-DEBUG: 03:38:24.372: score 10/40 157s (process:4242): libfprint-print-DEBUG: 03:38:24.379: score 10/40 157s (process:4242): libfprint-print-DEBUG: 03:38:24.386: score 10/40 157s (process:4242): libfprint-print-DEBUG: 03:38:24.393: score 10/40 157s (process:4242): libfprint-print-DEBUG: 03:38:24.400: score 10/40 157s (process:4242): libfprint-print-DEBUG: 03:38:24.614: score 855/40 157s (process:4242): libfprint-device-DEBUG: 03:38:24.614: Device reported identify result 157s (process:4242): libfprint-device-DEBUG: 03:38:24.614: Device reported identify completion 157s (process:4242): libfprint-device-DEBUG: 03:38:24.615: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 157s (process:4242): libfprint-device-DEBUG: 03:38:24.615: Updated temperature model after 0.28 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s (process:4242): libfprint-device-DEBUG: 03:38:24.615: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.615: Activating image device 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.615: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.615: Image device activation completed 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.615: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.615: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 157s (process:4242): libfprint-device-DEBUG: 03:38:24.615: Device reported finger status change: FP_FINGER_STATUS_NEEDED 157s (process:4242): libfprint-virtual_image-DEBUG: 03:38:24.615: image data: 0x4df69260 157s (process:4242): libfprint-device-DEBUG: 03:38:24.615: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.615: Image device reported finger status: on 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.615: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.615: Image device captured an image 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.615: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 157s (process:4242): libfprint-device-DEBUG: 03:38:24.616: Device reported finger status change: FP_FINGER_STATUS_PRESENT 157s (process:4242): libfprint-device-DEBUG: 03:38:24.616: Device reported finger status change: FP_FINGER_STATUS_NONE 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.616: Image device reported finger status: off 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.616: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.616: Deactivating image device 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.616: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.616: Image device deactivation completed 157s (process:4242): libfprint-image_device-DEBUG: 03:38:24.616: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 157s (process:4242): libfprint-image-DEBUG: 03:38:24.642: Minutiae scan completed in 0.027236 secs 158s (process:4242): libfprint-print-DEBUG: 03:38:25.702: score 1093/40 158s (process:4242): libfprint-device-DEBUG: 03:38:25.702: Device reported identify result 158s (process:4242): libfprint-device-DEBUG: 03:38:25.702: Device reported identify completion 158s (process:4242): libfprint-device-DEBUG: 03:38:25.702: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 158s (process:4242): libfprint-device-DEBUG: 03:38:25.702: Updated temperature model after 1.09 seconds, ratio 0.28 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 158s (process:4242): libfprint-device-DEBUG: 03:38:25.702: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.702: Activating image device 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.702: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.702: Image device activation completed 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.702: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.702: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 158s (process:4242): libfprint-device-DEBUG: 03:38:25.702: Device reported finger status change: FP_FINGER_STATUS_NEEDED 158s (process:4242): libfprint-device-DEBUG: 03:38:25.702: Device reported identify result 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.702: Deactivating image device 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.702: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.702: Image device deactivation completed 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.702: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 158s (process:4242): libfprint-device-DEBUG: 03:38:25.702: Device reported identify completion 158s (process:4242): libfprint-device-DEBUG: 03:38:25.702: Device reported finger status change: FP_FINGER_STATUS_NONE 158s (process:4242): libfprint-device-DEBUG: 03:38:25.703: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 158s (process:4242): libfprint-device-DEBUG: 03:38:25.703: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 158s (process:4242): libfprint-device-DEBUG: 03:38:25.703: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.703: Activating image device 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.703: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.703: Image device activation completed 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.703: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.703: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 158s (process:4242): libfprint-device-DEBUG: 03:38:25.703: Device reported finger status change: FP_FINGER_STATUS_NEEDED 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.703: Deactivating image device 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.703: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.703: Image device deactivation completed 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.703: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 158s (process:4242): libfprint-device-DEBUG: 03:38:25.703: Device reported generic error (An unspecified error occurred!) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 158s (process:4242): libfprint-device-DEBUG: 03:38:25.703: Device reported identify completion 158s (process:4242): libfprint-device-DEBUG: 03:38:25.703: Device reported finger status change: FP_FINGER_STATUS_NONE 158s (process:4242): libfprint-device-DEBUG: 03:38:25.703: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 158s (process:4242): libfprint-device-DEBUG: 03:38:25.703: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 158s (process:4242): libfprint-virtual_image-DEBUG: 03:38:25.703: 105511267: ../libfprint/drivers/virtual-image.c:244 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.803: Image device close completed 158s (process:4242): libfprint-device-DEBUG: 03:38:25.803: Device reported close completion 158s (process:4242): libfprint-device-DEBUG: 03:38:25.803: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 158s (process:4242): libfprint-device-DEBUG: 03:38:25.803: Updated temperature model after 0.10 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 158s Print was processed, continuing 158s Print was processed, continuing 158s Print was processed, continuing 158s Print was processed, continuing 158s Print was processed, continuing 158s Enroll done 158s Print was processed, continuing 158s Print was processed, continuing 158s Print was processed, continuing 158s Print was processed, continuing 158s Print was processed, continuing 158s Enroll done 158s Identify finished 158s Identify finished 158s Identify finished 158s fp - device - retry - quark: The swipe was too short, please try again. (1) 158s Identify finished 158s fp - device - error - quark: An unspecified error occurred! (0) 158s ok 158s test_verify_serialized (__main__.VirtualImage.test_verify_serialized) ... (process:4242): libfprint-virtual_image-DEBUG: 03:38:25.804: 105611851: ../libfprint/drivers/virtual-image.c:216 158s (process:4242): libfprint-virtual_device_connection-DEBUG: 03:38:25.804: 105611876: ../libfprint/drivers/virtual-device-listener.c:153 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.904: Image device open completed 158s (process:4242): libfprint-device-DEBUG: 03:38:25.904: Device reported open completion 158s (process:4242): libfprint-device-DEBUG: 03:38:25.904: Completing action FPI_DEVICE_ACTION_OPEN in idle! 158s (process:4242): libfprint-device-DEBUG: 03:38:25.904: Updated temperature model after 0.10 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 158s (process:4242): libfprint-device-DEBUG: 03:38:25.904: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.904: Activating image device 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.904: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.904: Image device activation completed 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.904: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.904: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 158s (process:4242): libfprint-device-DEBUG: 03:38:25.904: Device reported finger status change: FP_FINGER_STATUS_NEEDED 158s (process:4242): libfprint-virtual_device_connection-DEBUG: 03:38:25.904: Got a new connection! 158s (process:4242): libfprint-virtual_image-DEBUG: 03:38:25.905: image data: 0x4df69260 158s (process:4242): libfprint-device-DEBUG: 03:38:25.905: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.905: Image device reported finger status: on 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.905: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.905: Image device captured an image 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.905: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 158s (process:4242): libfprint-device-DEBUG: 03:38:25.905: Device reported finger status change: FP_FINGER_STATUS_PRESENT 158s (process:4242): libfprint-device-DEBUG: 03:38:25.905: Device reported finger status change: FP_FINGER_STATUS_NONE 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.905: Image device reported finger status: off 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.905: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 158s (process:4242): libfprint-image-DEBUG: 03:38:25.933: Minutiae scan completed in 0.028121 secs 158s (process:4242): libfprint-device-DEBUG: 03:38:25.934: Device reported enroll progress, reported 1 of 5 have been completed 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.934: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 158s (process:4242): libfprint-device-DEBUG: 03:38:25.934: Device reported finger status change: FP_FINGER_STATUS_NEEDED 158s (process:4242): libfprint-device-DEBUG: 03:38:25.934: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.934: Image device reported finger status: on 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.934: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 158s (process:4242): libfprint-virtual_image-DEBUG: 03:38:25.934: image data: 0x4df69260 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.934: Image device captured an image 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.934: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 158s (process:4242): libfprint-device-DEBUG: 03:38:25.934: Device reported finger status change: FP_FINGER_STATUS_PRESENT 158s (process:4242): libfprint-image-DEBUG: 03:38:25.962: Minutiae scan completed in 0.027442 secs 158s (process:4242): libfprint-device-DEBUG: 03:38:25.962: Device reported enroll progress, reported 2 of 5 have been completed 158s (process:4242): libfprint-device-DEBUG: 03:38:25.962: Device reported finger status change: FP_FINGER_STATUS_NONE 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.962: Image device reported finger status: off 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.962: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.962: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 158s (process:4242): libfprint-device-DEBUG: 03:38:25.963: Device reported finger status change: FP_FINGER_STATUS_NEEDED 158s (process:4242): libfprint-virtual_image-DEBUG: 03:38:25.963: image data: 0x4df69260 158s (process:4242): libfprint-device-DEBUG: 03:38:25.963: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.963: Image device reported finger status: on 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.963: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.963: Image device captured an image 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.963: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 158s (process:4242): libfprint-device-DEBUG: 03:38:25.963: Device reported finger status change: FP_FINGER_STATUS_PRESENT 158s (process:4242): libfprint-device-DEBUG: 03:38:25.963: Device reported finger status change: FP_FINGER_STATUS_NONE 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.963: Image device reported finger status: off 158s (process:4242): libfprint-image_device-DEBUG: 03:38:25.963: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 159s (process:4242): libfprint-image-DEBUG: 03:38:25.991: Minutiae scan completed in 0.027754 secs 159s (process:4242): libfprint-device-DEBUG: 03:38:25.991: Device reported enroll progress, reported 3 of 5 have been completed 159s (process:4242): libfprint-image_device-DEBUG: 03:38:25.992: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 159s (process:4242): libfprint-device-DEBUG: 03:38:25.992: Device reported finger status change: FP_FINGER_STATUS_NEEDED 159s (process:4242): libfprint-virtual_image-DEBUG: 03:38:25.992: image data: 0x4df69260 159s (process:4242): libfprint-device-DEBUG: 03:38:25.992: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 159s (process:4242): libfprint-image_device-DEBUG: 03:38:25.992: Image device reported finger status: on 159s (process:4242): libfprint-image_device-DEBUG: 03:38:25.992: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 159s (process:4242): libfprint-image_device-DEBUG: 03:38:25.992: Image device captured an image 159s (process:4242): libfprint-image_device-DEBUG: 03:38:25.992: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 159s (process:4242): libfprint-device-DEBUG: 03:38:25.992: Device reported finger status change: FP_FINGER_STATUS_PRESENT 159s (process:4242): libfprint-device-DEBUG: 03:38:25.992: Device reported finger status change: FP_FINGER_STATUS_NONE 159s (process:4242): libfprint-image_device-DEBUG: 03:38:25.993: Image device reported finger status: off 159s (process:4242): libfprint-image_device-DEBUG: 03:38:25.993: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 159s (process:4242): libfprint-image-DEBUG: 03:38:26.020: Minutiae scan completed in 0.027947 secs 159s (process:4242): libfprint-device-DEBUG: 03:38:26.020: Device reported enroll progress, reported 4 of 5 have been completed 159s (process:4242): libfprint-image_device-DEBUG: 03:38:26.021: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 159s (process:4242): libfprint-device-DEBUG: 03:38:26.021: Device reported finger status change: FP_FINGER_STATUS_NEEDED 159s (process:4242): libfprint-virtual_image-DEBUG: 03:38:26.021: image data: 0x4df69260 159s (process:4242): libfprint-device-DEBUG: 03:38:26.021: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 159s (process:4242): libfprint-image_device-DEBUG: 03:38:26.021: Image device reported finger status: on 159s (process:4242): libfprint-image_device-DEBUG: 03:38:26.021: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 159s (process:4242): libfprint-image_device-DEBUG: 03:38:26.021: Image device captured an image 159s (process:4242): libfprint-image_device-DEBUG: 03:38:26.021: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 159s (process:4242): libfprint-device-DEBUG: 03:38:26.024: Device reported finger status change: FP_FINGER_STATUS_PRESENT 159s (process:4242): libfprint-device-DEBUG: 03:38:26.024: Device reported finger status change: FP_FINGER_STATUS_NONE 159s (process:4242): libfprint-image_device-DEBUG: 03:38:26.024: Image device reported finger status: off 159s (process:4242): libfprint-image_device-DEBUG: 03:38:26.024: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 159s (process:4242): libfprint-image-DEBUG: 03:38:26.048: Minutiae scan completed in 0.027417 secs 159s (process:4242): libfprint-device-DEBUG: 03:38:26.049: Device reported enroll progress, reported 5 of 5 have been completed 159s (process:4242): libfprint-image_device-DEBUG: 03:38:26.049: Deactivating image device 159s (process:4242): libfprint-image_device-DEBUG: 03:38:26.049: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 159s (process:4242): libfprint-image_device-DEBUG: 03:38:26.049: Image device deactivation completed 159s (process:4242): libfprint-image_device-DEBUG: 03:38:26.049: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 159s (process:4242): libfprint-device-DEBUG: 03:38:26.049: Device reported enroll completion 159s (process:4242): libfprint-device-DEBUG: 03:38:26.049: Print for finger FP_FINGER_LEFT_THUMB enrolled 159s (process:4242): libfprint-device-DEBUG: 03:38:26.049: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 159s (process:4242): libfprint-device-DEBUG: 03:38:26.049: Updated temperature model after 0.14 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 159s (process:4242): libfprint-device-DEBUG: 03:38:26.049: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 159s (process:4242): libfprint-image_device-DEBUG: 03:38:26.049: Activating image device 159s (process:4242): libfprint-image_device-DEBUG: 03:38:26.049: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 159s (process:4242): libfprint-image_device-DEBUG: 03:38:26.049: Image device activation completed 159s (process:4242): libfprint-image_device-DEBUG: 03:38:26.049: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 159s (process:4242): libfprint-image_device-DEBUG: 03:38:26.049: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 159s (process:4242): libfprint-device-DEBUG: 03:38:26.049: Device reported finger status change: FP_FINGER_STATUS_NEEDED 159s (process:4242): libfprint-virtual_image-DEBUG: 03:38:26.049: image data: 0x4df86350 159s (process:4242): libfprint-device-DEBUG: 03:38:26.049: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 159s (process:4242): libfprint-image_device-DEBUG: 03:38:26.049: Image device reported finger status: on 159s (process:4242): libfprint-image_device-DEBUG: 03:38:26.049: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 159s (process:4242): libfprint-image_device-DEBUG: 03:38:26.049: Image device captured an image 159s (process:4242): libfprint-image_device-DEBUG: 03:38:26.050: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 159s (process:4242): libfprint-device-DEBUG: 03:38:26.050: Device reported finger status change: FP_FINGER_STATUS_PRESENT 159s (process:4242): libfprint-device-DEBUG: 03:38:26.050: Device reported finger status change: FP_FINGER_STATUS_NONE 159s (process:4242): libfprint-image_device-DEBUG: 03:38:26.050: Image device reported finger status: off 159s (process:4242): libfprint-image_device-DEBUG: 03:38:26.050: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 159s (process:4242): libfprint-image_device-DEBUG: 03:38:26.050: Deactivating image device 159s (process:4242): libfprint-image_device-DEBUG: 03:38:26.050: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 159s (process:4242): libfprint-image_device-DEBUG: 03:38:26.050: Image device deactivation completed 159s (process:4242): libfprint-image_device-DEBUG: 03:38:26.050: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 159s (process:4242): libfprint-image-DEBUG: 03:38:26.080: Minutiae scan completed in 0.029935 secs 159s Executing: libfprint-2/virtual-image.test 160s (process:4242): libfprint-print-DEBUG: 03:38:27.144: score 1093/40 160s (process:4242): libfprint-device-DEBUG: 03:38:27.144: Device reported verify result 160s (process:4242): libfprint-device-DEBUG: 03:38:27.144: Device reported verify completion 160s (process:4242): libfprint-device-DEBUG: 03:38:27.144: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 160s (process:4242): libfprint-device-DEBUG: 03:38:27.144: Updated temperature model after 1.10 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 160s (process:4242): libfprint-device-DEBUG: 03:38:27.144: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 160s (process:4242): libfprint-image_device-DEBUG: 03:38:27.144: Activating image device 160s (process:4242): libfprint-image_device-DEBUG: 03:38:27.144: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 160s (process:4242): libfprint-image_device-DEBUG: 03:38:27.144: Image device activation completed 160s (process:4242): libfprint-image_device-DEBUG: 03:38:27.144: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 160s (process:4242): libfprint-image_device-DEBUG: 03:38:27.144: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 160s (process:4242): libfprint-device-DEBUG: 03:38:27.144: Device reported finger status change: FP_FINGER_STATUS_NEEDED 160s (process:4242): libfprint-virtual_image-DEBUG: 03:38:27.145: image data: 0x4df782a0 160s (process:4242): libfprint-device-DEBUG: 03:38:27.145: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 160s (process:4242): libfprint-image_device-DEBUG: 03:38:27.145: Image device reported finger status: on 160s (process:4242): libfprint-image_device-DEBUG: 03:38:27.145: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 160s (process:4242): libfprint-image_device-DEBUG: 03:38:27.145: Image device captured an image 160s (process:4242): libfprint-image_device-DEBUG: 03:38:27.145: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 160s (process:4242): libfprint-device-DEBUG: 03:38:27.145: Device reported finger status change: FP_FINGER_STATUS_PRESENT 160s (process:4242): libfprint-device-DEBUG: 03:38:27.145: Device reported finger status change: FP_FINGER_STATUS_NONE 160s (process:4242): libfprint-image_device-DEBUG: 03:38:27.145: Image device reported finger status: off 160s (process:4242): libfprint-image_device-DEBUG: 03:38:27.145: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 160s (process:4242): libfprint-image_device-DEBUG: 03:38:27.145: Deactivating image device 160s (process:4242): libfprint-image_device-DEBUG: 03:38:27.145: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 160s (process:4242): libfprint-image_device-DEBUG: 03:38:27.145: Image device deactivation completed 160s (process:4242): libfprint-image_device-DEBUG: 03:38:27.145: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 160s (process:4242): libfprint-image-DEBUG: 03:38:27.172: Minutiae scan completed in 0.027595 secs 160s (process:4242): libfprint-print-DEBUG: 03:38:27.180: score 10/40 160s (process:4242): libfprint-print-DEBUG: 03:38:27.187: score 10/40 160s (process:4242): libfprint-print-DEBUG: 03:38:27.194: score 10/40 160s (process:4242): libfprint-print-DEBUG: 03:38:27.200: score 10/40 160s (process:4242): libfprint-print-DEBUG: 03:38:27.207: score 10/40 160s (process:4242): libfprint-device-DEBUG: 03:38:27.207: Device reported verify result 160s (process:4242): libfprint-device-DEBUG: 03:38:27.207: Device reported verify completion 160s (process:4242): libfprint-device-DEBUG: 03:38:27.207: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 160s (process:4242): libfprint-device-DEBUG: 03:38:27.207: Updated temperature model after 0.06 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 160s (process:4242): libfprint-virtual_image-DEBUG: 03:38:27.207: 107015426: ../libfprint/drivers/virtual-image.c:244 160s (process:4242): libfprint-image_device-DEBUG: 03:38:27.307: Image device close completed 160s (process:4242): libfprint-device-DEBUG: 03:38:27.307: Device reported close completion 160s (process:4242): libfprint-device-DEBUG: 03:38:27.307: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 160s (process:4242): libfprint-device-DEBUG: 03:38:27.307: Updated temperature model after 0.10 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 160s Print was processed, continuing 160s Print was processed, continuing 160s Print was processed, continuing 160s Print was processed, continuing 160s Print was processed, continuing 160s Enroll done 160s ok 160s 160s ---------------------------------------------------------------------- 160s Ran 5 tests in 6.757s 160s 160s OK 160s PASS: libfprint-2/virtual-image.test 160s Running test: libfprint-2/driver-uru4000-msv2.test 160s ** (umockdev-run:4252): DEBUG: 03:38:27.363: umockdev.vala:127: Created udev test bed /tmp/umockdev.9HH612 160s ** (umockdev-run:4252): DEBUG: 03:38:27.363: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10 160s ** (umockdev-run:4252): DEBUG: 03:38:27.365: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb) 160s ** (umockdev-run:4252): DEBUG: 03:38:27.367: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.9HH612/dev/bus/usb/001/047 160s ** (umockdev-run:4252): DEBUG: 03:38:27.367: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 160s ** (umockdev-run:4252): DEBUG: 03:38:27.368: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 160s ** (umockdev-run:4252): DEBUG: 03:38:27.371: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.9HH612/dev/bus/usb/001/001 160s ** (umockdev-run:4252): DEBUG: 03:38:27.371: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 160s ** (umockdev-run:4252): DEBUG: 03:38:27.372: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 160s (process:4256): libfprint-context-DEBUG: 03:38:27.457: Initializing FpContext (libfprint version 1.94.8+tod1) 160s (process:4256): libfprint-tod-DEBUG: 03:38:27.457: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 160s (process:4256): libfprint-context-DEBUG: 03:38:27.459: No driver found for USB device 1D6B:0002 160s (process:4256): libfprint-device-DEBUG: 03:38:27.459: Device reported probe completion 160s (process:4256): libfprint-device-DEBUG: 03:38:27.459: Completing action FPI_DEVICE_ACTION_PROBE in idle! 160s (process:4256): libfprint-device-DEBUG: 03:38:27.459: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 160s (process:4256): GLib-DEBUG: 03:38:27.461: setenv()/putenv() are not thread-safe and should not be used after threads are created 160s (process:4256): libfprint-image_device-DEBUG: 03:38:27.462: Image device open completed 160s (process:4256): libfprint-device-DEBUG: 03:38:27.462: Device reported open completion 160s (process:4256): libfprint-device-DEBUG: 03:38:27.462: Completing action FPI_DEVICE_ACTION_OPEN in idle! 160s (process:4256): libfprint-device-DEBUG: 03:38:27.462: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 160s (process:4256): libfprint-device-DEBUG: 03:38:27.462: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 160s (process:4256): libfprint-image_device-DEBUG: 03:38:27.462: Activating image device 160s (process:4256): libfprint-image_device-DEBUG: 03:38:27.463: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 160s (process:4256): libfprint-SSM-DEBUG: 03:38:27.463: [uru4000] INIT_NUM_STATES entering state 0 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.463: read 1 regs at 7 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.464: reg value 3 160s (process:4256): libfprint-SSM-DEBUG: 03:38:27.464: [uru4000] INIT_NUM_STATES entering state 1 160s (process:4256): libfprint-SSM-DEBUG: 03:38:27.464: [uru4000] INIT_NUM_STATES entering state 3 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.464: set 83 160s (process:4256): libfprint-SSM-DEBUG: 03:38:27.464: [uru4000] INIT_NUM_STATES entering state 4 160s (process:4256): libfprint-SSM-DEBUG: 03:38:27.464: [uru4000] POWERUP_NUM_STATES entering state 0 160s (process:4256): libfprint-SSM-DEBUG: 03:38:27.465: [uru4000] POWERUP_NUM_STATES entering state 1 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.465: set 03 160s (process:4256): libfprint-SSM-DEBUG: 03:38:27.465: [uru4000] POWERUP_NUM_STATES entering state 2 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.465: read 1 regs at 7 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.466: reg value 83 160s (process:4256): libfprint-SSM-DEBUG: 03:38:27.466: [uru4000] POWERUP_NUM_STATES entering state 3 160s (process:4256): libfprint-SSM-DEBUG: 03:38:27.466: [uru4000] POWERUP_NUM_STATES entering state 4 160s (process:4256): libfprint-SSM-DEBUG: 03:38:27.476: [uru4000] POWERUP_NUM_STATES entering state 5 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.476: 107283972: ../libfprint/drivers/uru4000.c:291 160s (process:4256): libfprint-SSM-DEBUG: 03:38:27.478: [uru4000] POWERUP_NUM_STATES entering state 6 160s (process:4256): libfprint-SSM-DEBUG: 03:38:27.478: [uru4000] POWERUP_NUM_STATES entering state 1 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.478: set 03 160s (process:4256): libfprint-SSM-DEBUG: 03:38:27.479: [uru4000] POWERUP_NUM_STATES entering state 2 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.479: read 1 regs at 7 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.479: reg value 3 160s (process:4256): libfprint-SSM-DEBUG: 03:38:27.479: [uru4000] POWERUP_NUM_STATES entering state 3 160s (process:4256): libfprint-SSM-DEBUG: 03:38:27.479: [uru4000] POWERUP_NUM_STATES completed successfully 160s (process:4256): libfprint-SSM-DEBUG: 03:38:27.479: [uru4000] INIT_NUM_STATES entering state 5 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.480: recv irq type 56aa 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.480: late scanpwr interrupt 160s (process:4256): libfprint-SSM-DEBUG: 03:38:27.480: [uru4000] INIT_NUM_STATES entering state 6 160s (process:4256): libfprint-SSM-DEBUG: 03:38:27.480: [uru4000] INIT_NUM_STATES entering state 7 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.480: read 16 regs at f0 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.481: reg value 50 160s (process:4256): libfprint-SSM-DEBUG: 03:38:27.481: [uru4000] INIT_NUM_STATES entering state 8 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.481: Versions 0059 and 0034 160s (process:4256): libfprint-SSM-DEBUG: 03:38:27.481: [uru4000] INIT_NUM_STATES completed successfully 160s (process:4256): libfprint-image_device-DEBUG: 03:38:27.481: Image device activation completed 160s (process:4256): libfprint-image_device-DEBUG: 03:38:27.481: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 160s (process:4256): libfprint-image_device-DEBUG: 03:38:27.481: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.481: wait finger on 160s (process:4256): libfprint-device-DEBUG: 03:38:27.482: Device reported finger status change: FP_FINGER_STATUS_NEEDED 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.483: recv irq type 0101 160s (process:4256): libfprint-device-DEBUG: 03:38:27.483: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 160s (process:4256): libfprint-image_device-DEBUG: 03:38:27.483: Image device reported finger status: on 160s (process:4256): libfprint-image_device-DEBUG: 03:38:27.483: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.483: starting capture 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.483: Image encryption seed: 1374298404 160s (process:4256): libfprint-SSM-DEBUG: 03:38:27.483: [uru4000] IMAGING_NUM_STATES entering state 0 160s (process:4256): libfprint-SSM-DEBUG: 03:38:27.486: [uru4000] IMAGING_NUM_STATES entering state 1 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.486: hw header lines 289 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.486: dev2: 10849 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.486: image seems to be encrypted 160s (process:4256): libfprint-SSM-DEBUG: 03:38:27.487: [uru4000] IMAGING_NUM_STATES entering state 2 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.487: read 4 regs at 34 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.489: reg value 7b 160s (process:4256): libfprint-SSM-DEBUG: 03:38:27.489: [uru4000] IMAGING_NUM_STATES entering state 3 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.489: encryption id 05 -> key db896f5f 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.489: 0 02 67 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.489: decoding 67 lines 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.489: 1 00 1 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.489: skipping 1 lines 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.489: 2 02 49 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.489: decoding 49 lines 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.490: 3 01 1 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.490: skipping 1 lines 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.490: 4 00 1 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.490: skipping 1 lines 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.490: 5 02 49 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.490: decoding 49 lines 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.490: 6 00 1 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.490: skipping 1 lines 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.490: 7 02 121 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.490: decoding 121 lines 160s (process:4256): libfprint-SSM-DEBUG: 03:38:27.490: [uru4000] IMAGING_NUM_STATES entering state 4 160s (process:4256): libfprint-image_device-DEBUG: 03:38:27.490: Image device captured an image 160s (process:4256): libfprint-image_device-DEBUG: 03:38:27.491: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 160s (process:4256): libfprint-device-DEBUG: 03:38:27.491: Device reported finger status change: FP_FINGER_STATUS_PRESENT 160s (process:4256): libfprint-SSM-DEBUG: 03:38:27.491: [uru4000] IMAGING_NUM_STATES completed successfully 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.491: await finger off 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.493: recv irq type 0200 160s (process:4256): libfprint-device-DEBUG: 03:38:27.493: Device reported finger status change: FP_FINGER_STATUS_NONE 160s (process:4256): libfprint-image_device-DEBUG: 03:38:27.493: Image device reported finger status: off 160s (process:4256): libfprint-image_device-DEBUG: 03:38:27.493: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 160s (process:4256): libfprint-image_device-DEBUG: 03:38:27.493: Deactivating image device 160s (process:4256): libfprint-image_device-DEBUG: 03:38:27.493: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.493: deactivating 160s (process:4256): libfprint-uru4000-DEBUG: 03:38:27.494: cancelled 160s (process:4256): libfprint-image_device-DEBUG: 03:38:27.494: Image device deactivation completed 160s (process:4256): libfprint-image_device-DEBUG: 03:38:27.494: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 160s (process:4256): libfprint-image-DEBUG: 03:38:27.533: Minutiae scan completed in 0.042188 secs 160s (process:4256): libfprint-device-DEBUG: 03:38:27.533: Device reported capture completion 160s (process:4256): libfprint-device-DEBUG: 03:38:27.533: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 160s (process:4256): libfprint-device-DEBUG: 03:38:27.533: Updated temperature model after 0.07 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 160s (process:4256): libfprint-image_device-DEBUG: 03:38:27.534: Image device close completed 160s (process:4256): libfprint-device-DEBUG: 03:38:27.534: Device reported close completion 160s (process:4256): libfprint-device-DEBUG: 03:38:27.534: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 160s (process:4256): libfprint-device-DEBUG: 03:38:27.534: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 160s ** (umockdev-run:4252): DEBUG: 03:38:27.742: umockdev.vala:154: Removing test bed /tmp/umockdev.9HH612 160s (umockdev-run:4252): GLib-DEBUG: 03:38:27.748: unsetenv() is not thread-safe and should not be used after threads are created 160s Comparing PNGs /tmp/libfprint-umockdev-test-9dt_fn17/capture.png and /usr/share/installed-tests/libfprint-2/uru4000-msv2/capture.png 160s PASS: libfprint-2/driver-uru4000-msv2.test 160s Running test: libfprint-2/driver-synaptics.test 160s ** (umockdev-run:4265): DEBUG: 03:38:27.830: umockdev.vala:127: Created udev test bed /tmp/umockdev.E0AJ22 160s ** (umockdev-run:4265): DEBUG: 03:38:27.830: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 160s ** (umockdev-run:4265): DEBUG: 03:38:27.831: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 160s ** (umockdev-run:4265): DEBUG: 03:38:27.835: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.E0AJ22/dev/bus/usb/001/004 160s ** (umockdev-run:4265): DEBUG: 03:38:27.835: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 160s ** (umockdev-run:4265): DEBUG: 03:38:27.836: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 160s ** (umockdev-run:4265): DEBUG: 03:38:27.839: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.E0AJ22/dev/bus/usb/001/001 160s ** (umockdev-run:4265): DEBUG: 03:38:27.839: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 160s ** (umockdev-run:4265): DEBUG: 03:38:27.839: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 160s (process:4269): libfprint-context-DEBUG: 03:38:27.921: Initializing FpContext (libfprint version 1.94.8+tod1) 160s (process:4269): libfprint-tod-DEBUG: 03:38:27.921: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 160s (process:4269): libfprint-context-DEBUG: 03:38:27.923: No driver found for USB device 1D6B:0002 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.924: 107731641: ../libfprint/drivers/synaptics/synaptics.c:1243 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.926: Build Time: 1596608839 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.926: Build Num: 3273255 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.926: Version: 10.1 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.926: Target: 1 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.926: Product: 65 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.926: sequence number is 1 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.926: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.926: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 160s (process:4269): libfprint-device-DEBUG: 03:38:27.927: Device reported probe completion 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.927: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 160s (process:4269): libfprint-device-DEBUG: 03:38:27.927: Completing action FPI_DEVICE_ACTION_PROBE in idle! 160s (process:4269): libfprint-device-DEBUG: 03:38:27.927: Not updating temperature model, device can run continuously! 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.929: 107736676: ../libfprint/drivers/synaptics/synaptics.c:1403 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.929: sequence number is 2 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.929: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.929: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 160s (process:4269): libfprint-device-DEBUG: 03:38:27.930: Device reported open completion 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.930: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 160s (process:4269): libfprint-device-DEBUG: 03:38:27.930: Completing action FPI_DEVICE_ACTION_OPEN in idle! 160s (process:4269): libfprint-device-DEBUG: 03:38:27.930: Not updating temperature model, device can run continuously! 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.930: clear all prints in database 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.930: sequence number is 3 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.930: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.931: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.931: Deleting All Enrolled Users is 0% complete 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.931: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.932: interrupt transfer done 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.932: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.933: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.933: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.933: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.933: Deleting All Enrolled Users is 100% complete 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.933: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.934: interrupt transfer done 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.934: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.935: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.935: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.935: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.935: Successfully deleted all enrolled user 160s (process:4269): libfprint-device-DEBUG: 03:38:27.935: Device reported deletion completion 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.935: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 160s (process:4269): libfprint-device-DEBUG: 03:38:27.935: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 160s (process:4269): libfprint-device-DEBUG: 03:38:27.935: Not updating temperature model, device can run continuously! 160s (process:4269): libfprint-device-DEBUG: 03:38:27.936: Not updating temperature model, device can run continuously! 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.936: 107744279: ../libfprint/drivers/synaptics/synaptics.c:1014 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.936: user_id: FP1-00000000-0-00000000-nobody, finger: 1 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.936: sequence number is 4 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.936: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.937: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 160s (process:4269): libfprint-device-DEBUG: 03:38:27.938: Device reported finger status change: FP_FINGER_STATUS_NEEDED 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.938: Place Finger on the Sensor! 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.938: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.938: interrupt transfer done 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.938: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.939: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.939: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.939: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 160s (process:4269): libfprint-device-DEBUG: 03:38:27.940: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.940: Finger is now on the sensor 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.940: Received message with 0 sequence number 0x91, ignoring! 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.940: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.945: interrupt transfer done 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.945: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.945: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.945: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.945: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.946: Fingerprint image capture complete! 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.946: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.947: interrupt transfer done 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.947: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.947: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.947: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.947: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 160s (process:4269): libfprint-device-DEBUG: 03:38:27.948: Device reported finger status change: FP_FINGER_STATUS_NEEDED 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.948: Finger is now off the sensor 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.948: Received message with 0 sequence number 0x91, ignoring! 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.948: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.948: interrupt transfer done 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.948: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.949: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.949: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.949: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.950: Enrollment is 12 % 160s (process:4269): libfprint-device-DEBUG: 03:38:27.950: Device reported enroll progress, reported 1 of 8 have been completed 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.950: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.950: interrupt transfer done 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.950: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.951: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.951: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.951: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 160s (process:4269): libfprint-device-DEBUG: 03:38:27.951: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.952: Finger is now on the sensor 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.952: Received message with 0 sequence number 0x91, ignoring! 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.952: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.952: interrupt transfer done 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.952: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.953: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.953: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.953: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.954: Fingerprint image capture complete! 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.954: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.954: interrupt transfer done 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.954: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.955: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.955: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.955: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 160s (process:4269): libfprint-device-DEBUG: 03:38:27.955: Device reported finger status change: FP_FINGER_STATUS_NEEDED 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.955: Finger is now off the sensor 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.955: Received message with 0 sequence number 0x91, ignoring! 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.955: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.956: interrupt transfer done 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.956: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.957: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.957: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.957: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.958: Enrollment is 25 % 160s (process:4269): libfprint-device-DEBUG: 03:38:27.958: Device reported enroll progress, reported 2 of 8 have been completed 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.958: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.958: interrupt transfer done 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.958: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.959: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.959: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.959: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 160s (process:4269): libfprint-device-DEBUG: 03:38:27.959: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.959: Finger is now on the sensor 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.959: Received message with 0 sequence number 0x91, ignoring! 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.959: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.960: interrupt transfer done 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.960: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.961: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.961: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.961: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 160s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.961: Fingerprint image capture complete! 160s (process:4269): libfprint-SSM-DEBUG: 03:38:27.961: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.962: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.962: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.963: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.963: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.963: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.963: Enrollment is 37 % 161s (process:4269): libfprint-device-DEBUG: 03:38:27.963: Device reported enroll progress, reported 3 of 8 have been completed 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.963: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.964: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.964: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.964: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.964: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.964: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-device-DEBUG: 03:38:27.965: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.965: Finger is now off the sensor 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.965: Received message with 0 sequence number 0x91, ignoring! 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.965: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.966: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.966: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.966: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.966: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.966: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-device-DEBUG: 03:38:27.967: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.967: Finger is now on the sensor 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.967: Received message with 0 sequence number 0x91, ignoring! 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.967: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.968: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.968: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.968: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.968: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.968: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.969: Fingerprint image capture complete! 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.969: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.969: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.969: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.970: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.970: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.970: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-device-DEBUG: 03:38:27.971: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.971: Finger is now off the sensor 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.971: Received message with 0 sequence number 0x91, ignoring! 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.971: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.971: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.971: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.972: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.972: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.972: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.972: Enrollment is 50 % 161s (process:4269): libfprint-device-DEBUG: 03:38:27.973: Device reported enroll progress, reported 4 of 8 have been completed 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.973: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.973: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.973: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.974: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.974: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.974: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-device-DEBUG: 03:38:27.974: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.974: Finger is now on the sensor 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.974: Received message with 0 sequence number 0x91, ignoring! 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.974: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.975: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.975: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.976: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.976: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.976: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.976: Fingerprint image capture complete! 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.976: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.977: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.977: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.977: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.977: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.977: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-device-DEBUG: 03:38:27.978: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.978: Finger is now off the sensor 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.978: Received message with 0 sequence number 0x91, ignoring! 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.978: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.979: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.979: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.979: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.979: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.979: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.980: Enrollment is 62 % 161s (process:4269): libfprint-device-DEBUG: 03:38:27.980: Device reported enroll progress, reported 5 of 8 have been completed 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.980: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.981: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.981: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.981: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.981: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.981: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-device-DEBUG: 03:38:27.982: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.982: Finger is now on the sensor 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.982: Received message with 0 sequence number 0x91, ignoring! 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.982: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.983: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.983: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.983: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.983: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.983: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.984: Fingerprint image capture complete! 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.984: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.984: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.985: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.985: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.985: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.985: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-device-DEBUG: 03:38:27.986: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.986: Finger is now off the sensor 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.986: Received message with 0 sequence number 0x91, ignoring! 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.986: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.987: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.987: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.987: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.987: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.987: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.988: Enrollment is 62 % 161s (process:4269): libfprint-device-DEBUG: 03:38:27.988: Device reported enroll progress, reported 5 of 8 have been completed 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.988: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.989: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.989: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.989: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.989: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.989: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-device-DEBUG: 03:38:27.990: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.990: Finger is now on the sensor 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.990: Received message with 0 sequence number 0x91, ignoring! 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.990: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.990: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.991: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.991: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.991: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.991: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.992: Fingerprint image capture complete! 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.992: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.993: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.993: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.993: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.993: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.993: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.994: Enrollment is 75 % 161s (process:4269): libfprint-device-DEBUG: 03:38:27.994: Device reported enroll progress, reported 6 of 8 have been completed 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.994: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.994: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.995: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.995: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.995: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.995: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-device-DEBUG: 03:38:27.996: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.996: Finger is now off the sensor 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.996: Received message with 0 sequence number 0x91, ignoring! 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.996: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.997: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.997: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.997: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.997: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.997: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-device-DEBUG: 03:38:27.998: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.998: Finger is now on the sensor 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.998: Received message with 0 sequence number 0x91, ignoring! 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.998: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:27.998: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.998: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.999: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.999: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:27.999: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.000: Fingerprint image capture complete! 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.000: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.001: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.001: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.002: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.002: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.002: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-device-DEBUG: 03:38:28.003: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.003: Finger is now off the sensor 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.003: Received message with 0 sequence number 0x91, ignoring! 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.003: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.004: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.004: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.004: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.004: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.004: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.005: Enrollment is 87 % 161s (process:4269): libfprint-device-DEBUG: 03:38:28.005: Device reported enroll progress, reported 7 of 8 have been completed 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.005: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.006: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.006: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.006: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.006: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.006: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-device-DEBUG: 03:38:28.007: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.007: Finger is now on the sensor 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.007: Received message with 0 sequence number 0x91, ignoring! 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.007: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.008: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.008: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.008: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.008: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.008: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.010: Fingerprint image capture complete! 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.010: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.011: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.011: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.011: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.011: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.011: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-device-DEBUG: 03:38:28.012: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.012: Finger is now off the sensor 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.012: Received message with 0 sequence number 0x91, ignoring! 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.012: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.013: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.013: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.014: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.014: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.014: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.014: Enrollment is 100 % 161s (process:4269): libfprint-device-DEBUG: 03:38:28.014: Device reported enroll progress, reported 8 of 8 have been completed 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.015: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.015: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.015: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.016: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.016: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.016: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-device-DEBUG: 03:38:28.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.017: Finger is now on the sensor 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.017: Received message with 0 sequence number 0x91, ignoring! 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.017: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.018: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.018: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.018: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.018: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.018: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-device-DEBUG: 03:38:28.019: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.019: Finger is now off the sensor 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.019: Received message with 0 sequence number 0x91, ignoring! 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.019: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.021: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.021: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.021: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.021: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.021: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.022: Enrollment was successful! 161s (process:4269): libfprint-device-DEBUG: 03:38:28.022: Device reported enroll completion 161s (process:4269): libfprint-device-DEBUG: 03:38:28.022: Device reported finger status change: FP_FINGER_STATUS_NONE 161s (process:4269): libfprint-device-DEBUG: 03:38:28.022: Print for finger FP_FINGER_UNKNOWN enrolled 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.022: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 161s (process:4269): libfprint-device-DEBUG: 03:38:28.022: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 161s (process:4269): libfprint-device-DEBUG: 03:38:28.022: Not updating temperature model, device can run continuously! 161s (process:4269): libfprint-device-DEBUG: 03:38:28.022: Not updating temperature model, device can run continuously! 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.022: data is 0x35354190 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.022: 107830615: ../libfprint/drivers/synaptics/synaptics.c:646 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.023: sequence number is 5 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.023: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.023: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-device-DEBUG: 03:38:28.024: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.024: Place Finger on the Sensor! 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.024: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.025: got suspend request 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.025: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.025: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 5 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.026: got resume request 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.026: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 6 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.026: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.027: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.027: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.028: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.028: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.028: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-device-DEBUG: 03:38:28.029: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.029: Finger is now on the sensor 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.029: Received message with 0 sequence number 0x91, ignoring! 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.029: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.030: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.030: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.031: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.031: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.031: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.033: Fingerprint image capture complete! 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.033: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.033: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.034: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.034: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.034: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.034: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-device-DEBUG: 03:38:28.035: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.035: Finger is now off the sensor 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.035: Received message with 0 sequence number 0x91, ignoring! 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.035: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.036: interrupt transfer done 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.036: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.036: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.036: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.036: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.037: Verify was successful! for user: FP1-00000000-0-00000000-nobody finger: 1 score: 61.800000 161s (process:4269): libfprint-device-DEBUG: 03:38:28.037: Device reported verify result 161s (process:4269): libfprint-device-DEBUG: 03:38:28.037: Device reported verify completion 161s (process:4269): libfprint-device-DEBUG: 03:38:28.037: Device reported finger status change: FP_FINGER_STATUS_NONE 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.037: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 161s (process:4269): libfprint-device-DEBUG: 03:38:28.037: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 161s (process:4269): libfprint-device-DEBUG: 03:38:28.037: Not updating temperature model, device can run continuously! 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.037: data is 0x35354190 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.037: 107845158: ../libfprint/drivers/synaptics/synaptics.c:1123 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.037: sequence number is 6 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.037: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.038: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.038: Successfully deleted enrolled user 161s (process:4269): libfprint-device-DEBUG: 03:38:28.038: Device reported deletion completion 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.038: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 161s (process:4269): libfprint-device-DEBUG: 03:38:28.038: Completing action FPI_DEVICE_ACTION_DELETE in idle! 161s (process:4269): libfprint-device-DEBUG: 03:38:28.038: Not updating temperature model, device can run continuously! 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.039: 107846630: ../libfprint/drivers/synaptics/synaptics.c:1424 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.039: sequence number is 7 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.039: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.039: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 161s (process:4269): libfprint-synaptics-DEBUG: 03:38:28.040: Fingerprint sensor ready to be powered down 161s (process:4269): libfprint-device-DEBUG: 03:38:28.040: Device reported close completion 161s (process:4269): libfprint-SSM-DEBUG: 03:38:28.040: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 161s (process:4269): libfprint-device-DEBUG: 03:38:28.040: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s (process:4269): libfprint-device-DEBUG: 03:38:28.040: Not updating temperature model, device can run continuously! 161s enrolling 161s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x6f6784c55980 (FpiDeviceSynaptics at 0x350c7f90)>, 1, None, None, None) 161s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x6f6784c55980 (FpiDeviceSynaptics at 0x350c7f90)>, 2, None, None, None) 161s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x6f6784c55980 (FpiDeviceSynaptics at 0x350c7f90)>, 3, None, None, None) 161s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x6f6784c55980 (FpiDeviceSynaptics at 0x350c7f90)>, 4, None, None, None) 161s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x6f6784c55980 (FpiDeviceSynaptics at 0x350c7f90)>, 5, None, None, None) 161s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x6f6784c55980 (FpiDeviceSynaptics at 0x350c7f90)>, 5, None, None, GLib.Error('Please try again.', 'fp - device - retry - quark', 0)) 161s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x6f6784c55980 (FpiDeviceSynaptics at 0x350c7f90)>, 6, None, None, None) 161s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x6f6784c55980 (FpiDeviceSynaptics at 0x350c7f90)>, 7, None, None, None) 161s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x6f6784c55980 (FpiDeviceSynaptics at 0x350c7f90)>, 8, None, None, None) 161s enroll done 161s verifying 161s verify done 161s deleting 161s delete done 161s libusb: warning [libusb_exit] device 1.1 still referenced 161s ** (umockdev-run:4265): DEBUG: 03:38:28.054: umockdev.vala:154: Removing test bed /tmp/umockdev.E0AJ22 161s (umockdev-run:4265): GLib-DEBUG: 03:38:28.060: unsetenv() is not thread-safe and should not be used after threads are created 161s PASS: libfprint-2/driver-synaptics.test 161s Running test: libfprint-2/driver-egismoc-05a1.test 161s ** (umockdev-run:4277): DEBUG: 03:38:28.102: umockdev.vala:127: Created udev test bed /tmp/umockdev.YCU012 161s ** (umockdev-run:4277): DEBUG: 03:38:28.102: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-5 161s ** (umockdev-run:4277): DEBUG: 03:38:28.104: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-5 (subsystem usb) 161s ** (umockdev-run:4277): DEBUG: 03:38:28.108: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.YCU012/dev/bus/usb/001/003 161s ** (umockdev-run:4277): DEBUG: 03:38:28.108: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 161s ** (umockdev-run:4277): DEBUG: 03:38:28.109: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 161s ** (umockdev-run:4277): DEBUG: 03:38:28.112: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.YCU012/dev/bus/usb/001/001 161s ** (umockdev-run:4277): DEBUG: 03:38:28.112: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 161s ** (umockdev-run:4277): DEBUG: 03:38:28.113: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 161s (process:4281): libfprint-context-DEBUG: 03:38:28.198: Initializing FpContext (libfprint version 1.94.8+tod1) 161s (process:4281): libfprint-tod-DEBUG: 03:38:28.198: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.200: 108008198: ../libfprint/drivers/egismoc/egismoc.c:1597 161s (process:4281): libfprint-context-DEBUG: 03:38:28.200: No driver found for USB device 1D6B:0002 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.200: egismoc_probe enter --> 161s (process:4281): libfprint-device-DEBUG: 03:38:28.202: Device reported probe completion 161s (process:4281): libfprint-device-DEBUG: 03:38:28.202: Completing action FPI_DEVICE_ACTION_PROBE in idle! 161s (process:4281): libfprint-device-DEBUG: 03:38:28.202: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.203: Opening device 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.203: [egismoc] DEV_INIT_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.204: [egismoc] DEV_INIT_STATES entering state 1 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.205: [egismoc] DEV_INIT_STATES entering state 2 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.207: [egismoc] DEV_INIT_STATES entering state 3 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.208: [egismoc] DEV_INIT_STATES entering state 4 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.208: [egismoc] DEV_INIT_STATES entering state 5 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.208: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.208: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.208: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.209: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.210: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.210: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.210: Firmware version callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.210: Response suffix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.210: Device firmware version is 9050.1.2.13 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.210: [egismoc] DEV_INIT_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.210: Task SSM done 161s (process:4281): libfprint-device-DEBUG: 03:38:28.210: Device reported open completion 161s (process:4281): libfprint-device-DEBUG: 03:38:28.210: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s (process:4281): libfprint-device-DEBUG: 03:38:28.210: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.211: List 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.211: [egismoc] LIST_STATES entering state 0 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.211: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.211: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.211: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.212: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.212: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.212: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.213: List callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.213: Device fingerprint 1: FP1-20231209-3-A9E16FBD-root 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.213: Device fingerprint 2: FP1-20231209-1-85DC4FAC-root 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.213: Device fingerprint 3: FP1-20231209-2-04EFB67C-root 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.213: Number of currently enrolled fingerprints on the device is 3 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.213: [egismoc] LIST_STATES entering state 1 161s (process:4281): libfprint-device-DEBUG: 03:38:28.213: Device reported listing completion 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.213: [egismoc] LIST_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.213: Task SSM done 161s (process:4281): libfprint-device-DEBUG: 03:38:28.213: Completing action FPI_DEVICE_ACTION_LIST in idle! 161s (process:4281): libfprint-device-DEBUG: 03:38:28.213: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.213: Clear storage 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.213: [egismoc] DELETE_STATES entering state 0 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.213: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.213: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.213: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.214: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.214: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.215: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.215: List callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.215: Device fingerprint 1: FP1-20231209-3-A9E16FBD-root 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.215: Device fingerprint 2: FP1-20231209-1-85DC4FAC-root 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.215: Device fingerprint 3: FP1-20231209-2-04EFB67C-root 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.215: Number of currently enrolled fingerprints on the device is 3 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.215: [egismoc] DELETE_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.215: Get delete command 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.215: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.215: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.215: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.215: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.216: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.216: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.216: Delete callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.216: Response prefix valid: yes 161s (process:4281): libfprint-device-DEBUG: 03:38:28.216: Device reported deletion completion 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.216: [egismoc] DELETE_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.216: Task SSM done 161s (process:4281): libfprint-device-DEBUG: 03:38:28.216: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 161s (process:4281): libfprint-device-DEBUG: 03:38:28.216: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.216: List 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.216: [egismoc] LIST_STATES entering state 0 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.216: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.216: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.216: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.216: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.217: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.217: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.217: List callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.217: Number of currently enrolled fingerprints on the device is 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.217: [egismoc] LIST_STATES entering state 1 161s (process:4281): libfprint-device-DEBUG: 03:38:28.217: Device reported listing completion 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.217: [egismoc] LIST_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.217: Task SSM done 161s (process:4281): libfprint-device-DEBUG: 03:38:28.217: Completing action FPI_DEVICE_ACTION_LIST in idle! 161s (process:4281): libfprint-device-DEBUG: 03:38:28.217: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s (process:4281): libfprint-device-DEBUG: 03:38:28.218: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.218: Enroll 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.218: [egismoc] ENROLL_STATES entering state 0 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.218: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.218: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.218: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.218: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.219: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.219: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.219: List callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.219: Number of currently enrolled fingerprints on the device is 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.219: [egismoc] ENROLL_STATES entering state 1 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.219: [egismoc] ENROLL_STATES entering state 2 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.219: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.219: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.219: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.219: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.220: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.220: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.220: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.220: [egismoc] ENROLL_STATES entering state 3 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.220: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.220: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.220: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.221: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.222: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.222: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.222: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.222: [egismoc] ENROLL_STATES entering state 4 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.222: Wait for finger on sensor 161s (process:4281): libfprint-device-DEBUG: 03:38:28.222: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.222: Finger on sensor callback 161s (process:4281): libfprint-device-DEBUG: 03:38:28.222: Device reported finger status change: FP_FINGER_STATUS_PRESENT 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.222: [egismoc] ENROLL_STATES entering state 5 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.222: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.222: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.222: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.223: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.223: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.223: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.223: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.223: [egismoc] ENROLL_STATES entering state 6 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.223: Get check command 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.223: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.223: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.223: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.224: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.225: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.225: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.225: Enroll check callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.225: Response suffix valid: yes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.225: [egismoc] ENROLL_STATES entering state 7 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.225: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.225: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.225: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.227: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.227: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.227: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.227: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.227: [egismoc] ENROLL_STATES entering state 8 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.227: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.227: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.227: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.228: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.228: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.228: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.228: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.228: [egismoc] ENROLL_STATES entering state 9 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.228: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.228: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.229: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.229: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.230: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.230: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.230: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.230: [egismoc] ENROLL_STATES entering state 10 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.230: Wait for finger on sensor 161s (process:4281): libfprint-device-DEBUG: 03:38:28.230: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.230: Finger on sensor callback 161s (process:4281): libfprint-device-DEBUG: 03:38:28.230: Device reported finger status change: FP_FINGER_STATUS_PRESENT 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.230: [egismoc] ENROLL_STATES entering state 11 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.230: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.230: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.230: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.231: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.232: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.232: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.232: Read capture callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.232: Response prefix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.232: Response suffix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.232: Partial capture successful. Please touch the sensor again (1/10) 161s (process:4281): libfprint-device-DEBUG: 03:38:28.232: Device reported enroll progress, reported 1 of 10 have been completed 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.232: [egismoc] ENROLL_STATES entering state 8 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.232: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.232: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.232: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.232: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.233: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.233: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.233: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.233: [egismoc] ENROLL_STATES entering state 9 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.233: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.233: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.233: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.233: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.234: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.234: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.234: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.234: [egismoc] ENROLL_STATES entering state 10 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.234: Wait for finger on sensor 161s (process:4281): libfprint-device-DEBUG: 03:38:28.234: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.235: Finger on sensor callback 161s (process:4281): libfprint-device-DEBUG: 03:38:28.235: Device reported finger status change: FP_FINGER_STATUS_PRESENT 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.235: [egismoc] ENROLL_STATES entering state 11 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.235: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.235: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.235: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.235: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.236: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.236: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.236: Read capture callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.236: Response prefix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.236: Response suffix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.236: Partial capture successful. Please touch the sensor again (2/10) 161s (process:4281): libfprint-device-DEBUG: 03:38:28.236: Device reported enroll progress, reported 2 of 10 have been completed 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.236: [egismoc] ENROLL_STATES entering state 8 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.236: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.236: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.236: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.236: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.237: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.237: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.237: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.237: [egismoc] ENROLL_STATES entering state 9 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.237: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.237: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.237: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.237: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.238: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.238: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.238: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.238: [egismoc] ENROLL_STATES entering state 10 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.238: Wait for finger on sensor 161s (process:4281): libfprint-device-DEBUG: 03:38:28.238: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.239: Finger on sensor callback 161s (process:4281): libfprint-device-DEBUG: 03:38:28.239: Device reported finger status change: FP_FINGER_STATUS_PRESENT 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.239: [egismoc] ENROLL_STATES entering state 11 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.239: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.239: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.239: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.239: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.240: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.240: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.240: Read capture callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.240: Response prefix valid: NO 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.240: Response prefix valid: NO 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.240: Response prefix valid: yes 161s (process:4281): libfprint-device-DEBUG: 03:38:28.240: Device reported enroll progress, reported 2 of 10 have been completed 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.240: [egismoc] ENROLL_STATES entering state 8 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.240: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.240: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.240: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.241: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.241: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.241: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.241: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.241: [egismoc] ENROLL_STATES entering state 9 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.241: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.241: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.241: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.242: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.242: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.242: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.242: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.242: [egismoc] ENROLL_STATES entering state 10 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.242: Wait for finger on sensor 161s (process:4281): libfprint-device-DEBUG: 03:38:28.242: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.243: Finger on sensor callback 161s (process:4281): libfprint-device-DEBUG: 03:38:28.243: Device reported finger status change: FP_FINGER_STATUS_PRESENT 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.243: [egismoc] ENROLL_STATES entering state 11 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.243: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.243: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.243: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.243: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.244: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.244: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.244: Read capture callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.244: Response prefix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.244: Response suffix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.244: Partial capture successful. Please touch the sensor again (3/10) 161s (process:4281): libfprint-device-DEBUG: 03:38:28.244: Device reported enroll progress, reported 3 of 10 have been completed 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.244: [egismoc] ENROLL_STATES entering state 8 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.244: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.244: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.244: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.245: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.245: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.245: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.245: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.245: [egismoc] ENROLL_STATES entering state 9 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.245: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.245: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.245: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.246: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.246: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.246: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.246: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.246: [egismoc] ENROLL_STATES entering state 10 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.246: Wait for finger on sensor 161s (process:4281): libfprint-device-DEBUG: 03:38:28.246: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.247: Finger on sensor callback 161s (process:4281): libfprint-device-DEBUG: 03:38:28.247: Device reported finger status change: FP_FINGER_STATUS_PRESENT 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.247: [egismoc] ENROLL_STATES entering state 11 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.247: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.247: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.247: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.247: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.248: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.248: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.248: Read capture callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.248: Response prefix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.248: Response suffix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.248: Partial capture successful. Please touch the sensor again (4/10) 161s (process:4281): libfprint-device-DEBUG: 03:38:28.248: Device reported enroll progress, reported 4 of 10 have been completed 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.248: [egismoc] ENROLL_STATES entering state 8 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.248: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.248: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.248: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.249: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.249: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.249: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.249: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.249: [egismoc] ENROLL_STATES entering state 9 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.249: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.249: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.249: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.250: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.250: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.250: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.250: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.250: [egismoc] ENROLL_STATES entering state 10 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.250: Wait for finger on sensor 161s (process:4281): libfprint-device-DEBUG: 03:38:28.250: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.251: Finger on sensor callback 161s (process:4281): libfprint-device-DEBUG: 03:38:28.251: Device reported finger status change: FP_FINGER_STATUS_PRESENT 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.251: [egismoc] ENROLL_STATES entering state 11 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.251: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.251: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.251: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.251: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.252: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.252: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.252: Read capture callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.252: Response prefix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.252: Response suffix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.252: Partial capture successful. Please touch the sensor again (5/10) 161s (process:4281): libfprint-device-DEBUG: 03:38:28.252: Device reported enroll progress, reported 5 of 10 have been completed 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.252: [egismoc] ENROLL_STATES entering state 8 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.252: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.252: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.252: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.253: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.253: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.253: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.253: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.253: [egismoc] ENROLL_STATES entering state 9 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.253: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.253: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.253: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.254: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.254: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.254: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.254: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.254: [egismoc] ENROLL_STATES entering state 10 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.254: Wait for finger on sensor 161s (process:4281): libfprint-device-DEBUG: 03:38:28.254: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.255: Finger on sensor callback 161s (process:4281): libfprint-device-DEBUG: 03:38:28.255: Device reported finger status change: FP_FINGER_STATUS_PRESENT 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.255: [egismoc] ENROLL_STATES entering state 11 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.255: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.255: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.255: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.255: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.256: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.256: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.256: Read capture callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.256: Response prefix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.256: Response suffix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.256: Partial capture successful. Please touch the sensor again (6/10) 161s (process:4281): libfprint-device-DEBUG: 03:38:28.256: Device reported enroll progress, reported 6 of 10 have been completed 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.256: [egismoc] ENROLL_STATES entering state 8 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.256: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.256: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.256: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.256: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.257: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.257: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.257: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.257: [egismoc] ENROLL_STATES entering state 9 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.257: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.257: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.257: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.258: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.258: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.258: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.258: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.258: [egismoc] ENROLL_STATES entering state 10 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.258: Wait for finger on sensor 161s (process:4281): libfprint-device-DEBUG: 03:38:28.258: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.259: Finger on sensor callback 161s (process:4281): libfprint-device-DEBUG: 03:38:28.259: Device reported finger status change: FP_FINGER_STATUS_PRESENT 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.259: [egismoc] ENROLL_STATES entering state 11 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.259: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.259: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.259: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.259: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.260: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.260: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.260: Read capture callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.260: Response prefix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.260: Response suffix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.260: Partial capture successful. Please touch the sensor again (7/10) 161s (process:4281): libfprint-device-DEBUG: 03:38:28.260: Device reported enroll progress, reported 7 of 10 have been completed 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.260: [egismoc] ENROLL_STATES entering state 8 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.260: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.260: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.260: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.260: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.261: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.261: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.261: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.261: [egismoc] ENROLL_STATES entering state 9 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.261: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.261: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.261: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.262: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.262: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.262: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.262: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.262: [egismoc] ENROLL_STATES entering state 10 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.262: Wait for finger on sensor 161s (process:4281): libfprint-device-DEBUG: 03:38:28.262: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.263: Finger on sensor callback 161s (process:4281): libfprint-device-DEBUG: 03:38:28.263: Device reported finger status change: FP_FINGER_STATUS_PRESENT 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.263: [egismoc] ENROLL_STATES entering state 11 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.263: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.263: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.263: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.263: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.264: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.264: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.264: Read capture callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.264: Response prefix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.264: Response suffix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.264: Partial capture successful. Please touch the sensor again (8/10) 161s (process:4281): libfprint-device-DEBUG: 03:38:28.264: Device reported enroll progress, reported 8 of 10 have been completed 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.264: [egismoc] ENROLL_STATES entering state 8 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.264: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.264: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.264: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.265: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.265: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.265: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.265: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.265: [egismoc] ENROLL_STATES entering state 9 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.265: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.265: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.265: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.266: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.266: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.266: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.266: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.266: [egismoc] ENROLL_STATES entering state 10 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.266: Wait for finger on sensor 161s (process:4281): libfprint-device-DEBUG: 03:38:28.266: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.267: Finger on sensor callback 161s (process:4281): libfprint-device-DEBUG: 03:38:28.267: Device reported finger status change: FP_FINGER_STATUS_PRESENT 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.267: [egismoc] ENROLL_STATES entering state 11 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.267: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.267: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.267: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.267: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.268: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.268: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.268: Read capture callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.268: Response prefix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.268: Response suffix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.268: Partial capture successful. Please touch the sensor again (9/10) 161s (process:4281): libfprint-device-DEBUG: 03:38:28.268: Device reported enroll progress, reported 9 of 10 have been completed 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.269: [egismoc] ENROLL_STATES entering state 8 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.269: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.269: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.269: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.269: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.270: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.270: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.270: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.270: [egismoc] ENROLL_STATES entering state 9 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.270: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.270: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.270: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.270: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.271: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.271: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.271: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.271: [egismoc] ENROLL_STATES entering state 10 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.271: Wait for finger on sensor 161s (process:4281): libfprint-device-DEBUG: 03:38:28.271: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.271: Finger on sensor callback 161s (process:4281): libfprint-device-DEBUG: 03:38:28.271: Device reported finger status change: FP_FINGER_STATUS_PRESENT 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.271: [egismoc] ENROLL_STATES entering state 11 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.271: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.271: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.271: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.272: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.272: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.272: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.272: Read capture callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.272: Response prefix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.272: Response suffix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.272: Partial capture successful. Please touch the sensor again (10/10) 161s (process:4281): libfprint-device-DEBUG: 03:38:28.272: Device reported enroll progress, reported 10 of 10 have been completed 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.273: [egismoc] ENROLL_STATES entering state 12 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.273: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.273: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.273: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.273: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.274: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.274: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.274: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.274: [egismoc] ENROLL_STATES entering state 13 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.274: New fingerprint ID: FP1-00000000-2-00000000-nobody 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.274: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.274: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.274: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.274: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.275: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.275: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.275: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.275: [egismoc] ENROLL_STATES entering state 14 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.275: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.275: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.275: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.275: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.276: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.276: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.276: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.276: [egismoc] ENROLL_STATES entering state 15 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.276: Enrollment was successful! 161s (process:4281): libfprint-device-DEBUG: 03:38:28.276: Device reported enroll completion 161s (process:4281): libfprint-device-DEBUG: 03:38:28.276: Device reported finger status change: FP_FINGER_STATUS_NONE 161s (process:4281): libfprint-device-DEBUG: 03:38:28.276: Print for finger FP_FINGER_LEFT_INDEX enrolled 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.276: [egismoc] ENROLL_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.276: Task SSM done 161s (process:4281): libfprint-device-DEBUG: 03:38:28.276: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 161s (process:4281): libfprint-device-DEBUG: 03:38:28.276: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.276: List 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.276: [egismoc] LIST_STATES entering state 0 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.276: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.276: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.276: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.277: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.277: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.277: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.277: List callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.277: Device fingerprint 1: FP1-00000000-2-00000000-nobody 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.277: Number of currently enrolled fingerprints on the device is 1 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.277: [egismoc] LIST_STATES entering state 1 161s (process:4281): libfprint-device-DEBUG: 03:38:28.277: Device reported listing completion 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.277: [egismoc] LIST_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.277: Task SSM done 161s (process:4281): libfprint-device-DEBUG: 03:38:28.277: Completing action FPI_DEVICE_ACTION_LIST in idle! 161s (process:4281): libfprint-device-DEBUG: 03:38:28.277: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s (process:4281): libfprint-device-DEBUG: 03:38:28.278: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.278: Identify or Verify 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.278: [egismoc] IDENTIFY_STATES entering state 0 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.278: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.278: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.278: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.278: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.279: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.279: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.279: List callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.279: Device fingerprint 1: FP1-00000000-2-00000000-nobody 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.279: Number of currently enrolled fingerprints on the device is 1 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.279: [egismoc] IDENTIFY_STATES entering state 1 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.279: [egismoc] IDENTIFY_STATES entering state 2 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.279: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.279: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.279: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.280: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.280: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.280: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.280: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.280: [egismoc] IDENTIFY_STATES entering state 3 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.280: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.280: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.280: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.281: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.282: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.282: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.282: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.282: [egismoc] IDENTIFY_STATES entering state 4 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.282: Wait for finger on sensor 161s (process:4281): libfprint-device-DEBUG: 03:38:28.282: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.282: Finger on sensor callback 161s (process:4281): libfprint-device-DEBUG: 03:38:28.282: Device reported finger status change: FP_FINGER_STATUS_PRESENT 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.282: [egismoc] IDENTIFY_STATES entering state 5 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.282: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.282: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.282: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.284: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.285: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.285: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.285: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.285: [egismoc] IDENTIFY_STATES entering state 6 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.285: Get check command 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.285: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.285: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.285: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.286: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.286: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.286: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.286: Identify check callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.286: Response suffix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.286: Identify successful for: FP1-00000000-2-00000000-nobody 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.286: Verifying against: FP1-00000000-2-00000000-nobody 161s (process:4281): libfprint-device-DEBUG: 03:38:28.286: Device reported verify result 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.286: [egismoc] IDENTIFY_STATES entering state 7 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.286: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.286: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.286: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.287: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.287: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.287: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.287: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.288: [egismoc] IDENTIFY_STATES entering state 8 161s (process:4281): libfprint-device-DEBUG: 03:38:28.288: Device reported verify completion 161s (process:4281): libfprint-device-DEBUG: 03:38:28.288: Device reported finger status change: FP_FINGER_STATUS_NONE 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.288: [egismoc] IDENTIFY_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.288: Task SSM done 161s (process:4281): libfprint-device-DEBUG: 03:38:28.288: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 161s (process:4281): libfprint-device-DEBUG: 03:38:28.288: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s (process:4281): libfprint-device-DEBUG: 03:38:28.288: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.288: Identify or Verify 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.288: [egismoc] IDENTIFY_STATES entering state 0 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.288: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.288: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.288: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.289: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.290: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.290: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.290: List callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.290: Device fingerprint 1: FP1-00000000-2-00000000-nobody 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.290: Number of currently enrolled fingerprints on the device is 1 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.290: [egismoc] IDENTIFY_STATES entering state 1 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.290: [egismoc] IDENTIFY_STATES entering state 2 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.290: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.290: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.290: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.291: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.292: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.292: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.292: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.292: [egismoc] IDENTIFY_STATES entering state 3 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.292: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.292: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.292: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.293: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.293: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.293: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.293: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.293: [egismoc] IDENTIFY_STATES entering state 4 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.293: Wait for finger on sensor 161s (process:4281): libfprint-device-DEBUG: 03:38:28.293: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.294: Finger on sensor callback 161s (process:4281): libfprint-device-DEBUG: 03:38:28.294: Device reported finger status change: FP_FINGER_STATUS_PRESENT 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.294: [egismoc] IDENTIFY_STATES entering state 5 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.294: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.294: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.294: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.294: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.295: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.295: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.295: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.295: [egismoc] IDENTIFY_STATES entering state 6 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.295: Get check command 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.295: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.295: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.295: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.296: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.296: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.296: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.296: Identify check callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.296: Response suffix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.296: Identify successful for: FP1-00000000-2-00000000-nobody 161s (process:4281): libfprint-device-DEBUG: 03:38:28.297: Device reported identify result 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.297: [egismoc] IDENTIFY_STATES entering state 7 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.297: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.297: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.297: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.297: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.298: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.298: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.298: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.298: [egismoc] IDENTIFY_STATES entering state 8 161s (process:4281): libfprint-device-DEBUG: 03:38:28.298: Device reported identify completion 161s (process:4281): libfprint-device-DEBUG: 03:38:28.298: Device reported finger status change: FP_FINGER_STATUS_NONE 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.298: [egismoc] IDENTIFY_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.298: Task SSM done 161s (process:4281): libfprint-device-DEBUG: 03:38:28.298: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 161s (process:4281): libfprint-device-DEBUG: 03:38:28.298: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s (process:4281): libfprint-device-DEBUG: 03:38:28.298: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.298: Enroll 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.298: [egismoc] ENROLL_STATES entering state 0 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.298: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.298: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.298: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.299: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.300: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.300: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.300: List callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.300: Device fingerprint 1: FP1-00000000-2-00000000-nobody 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.300: Number of currently enrolled fingerprints on the device is 1 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.300: [egismoc] ENROLL_STATES entering state 1 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.300: [egismoc] ENROLL_STATES entering state 2 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.300: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.300: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.300: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.301: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.301: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.302: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.302: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.302: [egismoc] ENROLL_STATES entering state 3 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.302: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.302: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.302: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.302: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.303: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.303: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.303: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.303: [egismoc] ENROLL_STATES entering state 4 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.303: Wait for finger on sensor 161s (process:4281): libfprint-device-DEBUG: 03:38:28.303: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.303: Finger on sensor callback 161s (process:4281): libfprint-device-DEBUG: 03:38:28.303: Device reported finger status change: FP_FINGER_STATUS_PRESENT 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.303: [egismoc] ENROLL_STATES entering state 5 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.303: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.303: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.303: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.304: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.305: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.305: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.305: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.305: [egismoc] ENROLL_STATES entering state 6 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.305: Get check command 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.305: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.305: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.305: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.305: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.306: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.306: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.306: Enroll check callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.306: Response suffix valid: NO 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.306: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.306: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.306: Task SSM done 161s (process:4281): libfprint-device-DEBUG: 03:38:28.306: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL 161s (process:4281): libfprint-device-DEBUG: 03:38:28.306: Device reported enroll completion 161s (process:4281): libfprint-device-DEBUG: 03:38:28.306: Device reported finger status change: FP_FINGER_STATUS_NONE 161s (process:4281): libfprint-device-DEBUG: 03:38:28.306: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 161s (process:4281): libfprint-device-DEBUG: 03:38:28.306: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.306: List 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.306: [egismoc] LIST_STATES entering state 0 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.306: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.306: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.306: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.307: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.308: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.308: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.308: List callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.308: Device fingerprint 1: FP1-00000000-2-00000000-nobody 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.308: Number of currently enrolled fingerprints on the device is 1 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.308: [egismoc] LIST_STATES entering state 1 161s (process:4281): libfprint-device-DEBUG: 03:38:28.308: Device reported listing completion 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.308: [egismoc] LIST_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.308: Task SSM done 161s (process:4281): libfprint-device-DEBUG: 03:38:28.308: Completing action FPI_DEVICE_ACTION_LIST in idle! 161s (process:4281): libfprint-device-DEBUG: 03:38:28.308: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s (process:4281): libfprint-device-DEBUG: 03:38:28.308: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.308: Enroll 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.308: [egismoc] ENROLL_STATES entering state 0 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.308: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.308: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.308: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.309: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.309: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.309: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.309: List callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.309: Device fingerprint 1: FP1-00000000-2-00000000-nobody 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.309: Number of currently enrolled fingerprints on the device is 1 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.309: [egismoc] ENROLL_STATES entering state 1 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.309: [egismoc] ENROLL_STATES entering state 2 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.309: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.309: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.309: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.310: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.311: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.311: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.311: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.311: [egismoc] ENROLL_STATES entering state 3 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.311: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.311: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.311: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.311: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.312: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.312: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.312: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.312: [egismoc] ENROLL_STATES entering state 4 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.312: Wait for finger on sensor 161s (process:4281): libfprint-device-DEBUG: 03:38:28.312: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.313: Finger on sensor callback 161s (process:4281): libfprint-device-DEBUG: 03:38:28.313: Device reported finger status change: FP_FINGER_STATUS_PRESENT 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.313: [egismoc] ENROLL_STATES entering state 5 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.313: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.313: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.313: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.313: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.314: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.314: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.314: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.314: [egismoc] ENROLL_STATES entering state 6 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.314: Get check command 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.314: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.314: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.314: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.314: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.315: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.315: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.315: Enroll check callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.315: Response suffix valid: yes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.315: [egismoc] ENROLL_STATES entering state 7 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.315: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.315: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.315: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.315: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.316: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.316: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.316: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.316: [egismoc] ENROLL_STATES entering state 8 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.316: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.316: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.316: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.316: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.317: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.317: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.317: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.317: [egismoc] ENROLL_STATES entering state 9 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.317: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.317: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.317: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.317: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.318: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.318: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.318: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.318: [egismoc] ENROLL_STATES entering state 10 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.318: Wait for finger on sensor 161s (process:4281): libfprint-device-DEBUG: 03:38:28.318: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.319: Finger on sensor callback 161s (process:4281): libfprint-device-DEBUG: 03:38:28.319: Device reported finger status change: FP_FINGER_STATUS_PRESENT 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.319: [egismoc] ENROLL_STATES entering state 11 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.319: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.319: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.319: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.319: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.320: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.320: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.320: Read capture callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.320: Response prefix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.320: Response suffix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.320: Partial capture successful. Please touch the sensor again (1/10) 161s (process:4281): libfprint-device-DEBUG: 03:38:28.320: Device reported enroll progress, reported 1 of 10 have been completed 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.320: [egismoc] ENROLL_STATES entering state 8 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.320: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.320: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.320: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.320: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.321: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.321: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.321: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.321: [egismoc] ENROLL_STATES entering state 9 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.321: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.321: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.321: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.322: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.322: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.322: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.322: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.322: [egismoc] ENROLL_STATES entering state 10 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.322: Wait for finger on sensor 161s (process:4281): libfprint-device-DEBUG: 03:38:28.322: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.323: Finger on sensor callback 161s (process:4281): libfprint-device-DEBUG: 03:38:28.323: Device reported finger status change: FP_FINGER_STATUS_PRESENT 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.323: [egismoc] ENROLL_STATES entering state 11 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.323: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.323: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.323: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.324: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.324: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.324: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.324: Read capture callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.324: Response prefix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.324: Response suffix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.324: Partial capture successful. Please touch the sensor again (2/10) 161s (process:4281): libfprint-device-DEBUG: 03:38:28.324: Device reported enroll progress, reported 2 of 10 have been completed 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.324: [egismoc] ENROLL_STATES entering state 8 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.324: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.324: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.324: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.329: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.329: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.329: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.330: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.330: [egismoc] ENROLL_STATES entering state 9 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.330: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.330: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.330: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.330: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.331: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.331: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.331: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.331: [egismoc] ENROLL_STATES entering state 10 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.331: Wait for finger on sensor 161s (process:4281): libfprint-device-DEBUG: 03:38:28.331: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.331: Finger on sensor callback 161s (process:4281): libfprint-device-DEBUG: 03:38:28.331: Device reported finger status change: FP_FINGER_STATUS_PRESENT 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.331: [egismoc] ENROLL_STATES entering state 11 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.331: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.331: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.331: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.332: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.332: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.332: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.333: Read capture callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.333: Response prefix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.333: Response suffix valid: NO 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.333: Response prefix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.333: Response suffix valid: yes 161s (process:4281): libfprint-device-DEBUG: 03:38:28.333: Device reported enroll progress, reported 2 of 10 have been completed 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.333: [egismoc] ENROLL_STATES entering state 8 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.333: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.333: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.333: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.333: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.334: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.334: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.334: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.334: [egismoc] ENROLL_STATES entering state 9 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.334: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.334: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.334: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.334: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.335: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.335: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.335: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.335: [egismoc] ENROLL_STATES entering state 10 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.335: Wait for finger on sensor 161s (process:4281): libfprint-device-DEBUG: 03:38:28.335: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.336: Finger on sensor callback 161s (process:4281): libfprint-device-DEBUG: 03:38:28.336: Device reported finger status change: FP_FINGER_STATUS_PRESENT 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.336: [egismoc] ENROLL_STATES entering state 11 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.336: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.336: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.336: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.336: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.337: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.337: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.337: Read capture callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.337: Response prefix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.337: Response suffix valid: NO 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.337: Response prefix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.337: Response suffix valid: yes 161s (process:4281): libfprint-device-DEBUG: 03:38:28.337: Device reported enroll progress, reported 2 of 10 have been completed 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.337: [egismoc] ENROLL_STATES entering state 8 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.337: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.337: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.337: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.337: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.338: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.338: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.338: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.338: [egismoc] ENROLL_STATES entering state 9 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.338: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.338: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.338: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.339: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.339: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.339: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.339: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.339: [egismoc] ENROLL_STATES entering state 10 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.339: Wait for finger on sensor 161s (process:4281): libfprint-device-DEBUG: 03:38:28.339: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.340: Finger on sensor callback 161s (process:4281): libfprint-device-DEBUG: 03:38:28.340: Device reported finger status change: FP_FINGER_STATUS_PRESENT 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.340: [egismoc] ENROLL_STATES entering state 11 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.340: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.340: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.340: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.340: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.341: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.341: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.341: Read capture callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.341: Response prefix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.341: Response suffix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.341: Partial capture successful. Please touch the sensor again (3/10) 161s (process:4281): libfprint-device-DEBUG: 03:38:28.341: Device reported enroll progress, reported 3 of 10 have been completed 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.341: [egismoc] ENROLL_STATES entering state 8 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.341: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.341: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.341: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.342: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.342: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.342: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.342: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.342: [egismoc] ENROLL_STATES entering state 9 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.342: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.342: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.342: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.343: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.343: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.343: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.343: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.343: [egismoc] ENROLL_STATES entering state 10 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.343: Wait for finger on sensor 161s (process:4281): libfprint-device-DEBUG: 03:38:28.343: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.344: Finger on sensor callback 161s (process:4281): libfprint-device-DEBUG: 03:38:28.344: Device reported finger status change: FP_FINGER_STATUS_PRESENT 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.344: [egismoc] ENROLL_STATES entering state 11 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.344: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.344: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.344: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.345: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.345: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.345: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.345: Read capture callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.345: Response prefix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.345: Response suffix valid: NO 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.345: Response prefix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.345: Response suffix valid: yes 161s (process:4281): libfprint-device-DEBUG: 03:38:28.345: Device reported enroll progress, reported 3 of 10 have been completed 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.345: [egismoc] ENROLL_STATES entering state 8 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.345: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.345: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.345: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.346: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.347: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.347: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.347: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.347: [egismoc] ENROLL_STATES entering state 9 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.347: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.347: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.347: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.347: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.348: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.348: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.348: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.348: [egismoc] ENROLL_STATES entering state 10 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.348: Wait for finger on sensor 161s (process:4281): libfprint-device-DEBUG: 03:38:28.348: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.355: Finger on sensor callback 161s (process:4281): libfprint-device-DEBUG: 03:38:28.355: Device reported finger status change: FP_FINGER_STATUS_PRESENT 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.355: [egismoc] ENROLL_STATES entering state 11 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.355: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.355: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.355: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.355: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.357: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.357: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.357: Read capture callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.357: Response prefix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.357: Response suffix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.357: Partial capture successful. Please touch the sensor again (4/10) 161s (process:4281): libfprint-device-DEBUG: 03:38:28.357: Device reported enroll progress, reported 4 of 10 have been completed 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.357: [egismoc] ENROLL_STATES entering state 8 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.357: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.357: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.357: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.357: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.359: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.359: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.359: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.359: [egismoc] ENROLL_STATES entering state 9 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.359: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.359: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.359: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.359: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.360: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.360: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.360: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.360: [egismoc] ENROLL_STATES entering state 10 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.360: Wait for finger on sensor 161s (process:4281): libfprint-device-DEBUG: 03:38:28.360: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.360: Finger on sensor callback 161s (process:4281): libfprint-device-DEBUG: 03:38:28.360: Device reported finger status change: FP_FINGER_STATUS_PRESENT 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.360: [egismoc] ENROLL_STATES entering state 11 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.360: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.361: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.361: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.364: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.365: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.365: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.365: Read capture callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.365: Response prefix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.365: Response suffix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.365: Partial capture successful. Please touch the sensor again (5/10) 161s (process:4281): libfprint-device-DEBUG: 03:38:28.365: Device reported enroll progress, reported 5 of 10 have been completed 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.365: [egismoc] ENROLL_STATES entering state 8 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.365: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.365: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.365: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.365: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.366: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.366: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.366: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.366: [egismoc] ENROLL_STATES entering state 9 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.366: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.366: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.366: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.367: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.367: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.367: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.367: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.367: [egismoc] ENROLL_STATES entering state 10 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.367: Wait for finger on sensor 161s (process:4281): libfprint-device-DEBUG: 03:38:28.367: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.368: Finger on sensor callback 161s (process:4281): libfprint-device-DEBUG: 03:38:28.368: Device reported finger status change: FP_FINGER_STATUS_PRESENT 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.368: [egismoc] ENROLL_STATES entering state 11 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.368: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.368: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.368: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.368: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.369: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.369: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.369: Read capture callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.369: Response prefix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.369: Response suffix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.369: Partial capture successful. Please touch the sensor again (6/10) 161s (process:4281): libfprint-device-DEBUG: 03:38:28.369: Device reported enroll progress, reported 6 of 10 have been completed 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.369: [egismoc] ENROLL_STATES entering state 8 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.369: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.369: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.369: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.370: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.370: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.370: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.370: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.370: [egismoc] ENROLL_STATES entering state 9 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.370: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.370: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.370: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.371: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.371: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.371: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.372: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.372: [egismoc] ENROLL_STATES entering state 10 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.372: Wait for finger on sensor 161s (process:4281): libfprint-device-DEBUG: 03:38:28.372: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.372: Finger on sensor callback 161s (process:4281): libfprint-device-DEBUG: 03:38:28.372: Device reported finger status change: FP_FINGER_STATUS_PRESENT 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.372: [egismoc] ENROLL_STATES entering state 11 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.372: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.372: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.372: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.373: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.373: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.373: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.373: Read capture callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.373: Response prefix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.373: Response suffix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.373: Partial capture successful. Please touch the sensor again (7/10) 161s (process:4281): libfprint-device-DEBUG: 03:38:28.373: Device reported enroll progress, reported 7 of 10 have been completed 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.373: [egismoc] ENROLL_STATES entering state 8 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.373: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.373: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.373: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.374: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.374: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.374: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.375: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.375: [egismoc] ENROLL_STATES entering state 9 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.375: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.375: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.375: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.375: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.376: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.376: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.376: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.376: [egismoc] ENROLL_STATES entering state 10 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.376: Wait for finger on sensor 161s (process:4281): libfprint-device-DEBUG: 03:38:28.376: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.376: Finger on sensor callback 161s (process:4281): libfprint-device-DEBUG: 03:38:28.376: Device reported finger status change: FP_FINGER_STATUS_PRESENT 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.376: [egismoc] ENROLL_STATES entering state 11 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.376: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.376: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.376: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.377: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.377: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.377: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.377: Read capture callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.377: Response prefix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.377: Response suffix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.377: Partial capture successful. Please touch the sensor again (8/10) 161s (process:4281): libfprint-device-DEBUG: 03:38:28.377: Device reported enroll progress, reported 8 of 10 have been completed 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.377: [egismoc] ENROLL_STATES entering state 8 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.377: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.377: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.377: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.378: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.378: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.378: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.378: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.378: [egismoc] ENROLL_STATES entering state 9 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.378: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.378: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.378: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.379: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.379: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.379: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.379: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.379: [egismoc] ENROLL_STATES entering state 10 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.379: Wait for finger on sensor 161s (process:4281): libfprint-device-DEBUG: 03:38:28.379: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.380: Finger on sensor callback 161s (process:4281): libfprint-device-DEBUG: 03:38:28.380: Device reported finger status change: FP_FINGER_STATUS_PRESENT 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.380: [egismoc] ENROLL_STATES entering state 11 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.380: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.380: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.380: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.381: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.385: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.385: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.385: Read capture callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.385: Response prefix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.385: Response suffix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.385: Partial capture successful. Please touch the sensor again (9/10) 161s (process:4281): libfprint-device-DEBUG: 03:38:28.385: Device reported enroll progress, reported 9 of 10 have been completed 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.385: [egismoc] ENROLL_STATES entering state 8 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.385: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.385: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.385: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.385: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.386: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.386: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.386: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.386: [egismoc] ENROLL_STATES entering state 9 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.386: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.386: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.386: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.387: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.387: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.387: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.387: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.387: [egismoc] ENROLL_STATES entering state 10 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.387: Wait for finger on sensor 161s (process:4281): libfprint-device-DEBUG: 03:38:28.387: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.388: Finger on sensor callback 161s (process:4281): libfprint-device-DEBUG: 03:38:28.388: Device reported finger status change: FP_FINGER_STATUS_PRESENT 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.388: [egismoc] ENROLL_STATES entering state 11 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.388: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.388: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.388: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.389: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.389: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.389: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.389: Read capture callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.389: Response prefix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.389: Response suffix valid: yes 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.389: Partial capture successful. Please touch the sensor again (10/10) 161s (process:4281): libfprint-device-DEBUG: 03:38:28.389: Device reported enroll progress, reported 10 of 10 have been completed 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.389: [egismoc] ENROLL_STATES entering state 12 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.389: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.389: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.389: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.393: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.393: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.393: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.393: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.393: [egismoc] ENROLL_STATES entering state 13 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.393: New fingerprint ID: FP1-00000000-7-00000000-nobody 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.393: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.393: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.394: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.394: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.395: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.395: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.395: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.395: [egismoc] ENROLL_STATES entering state 14 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.395: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.395: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.395: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.395: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.396: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.396: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.396: Task SSM next state callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.396: [egismoc] ENROLL_STATES entering state 15 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.396: Enrollment was successful! 161s (process:4281): libfprint-device-DEBUG: 03:38:28.396: Device reported enroll completion 161s (process:4281): libfprint-device-DEBUG: 03:38:28.396: Device reported finger status change: FP_FINGER_STATUS_NONE 161s (process:4281): libfprint-device-DEBUG: 03:38:28.396: Print for finger FP_FINGER_RIGHT_INDEX enrolled 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.396: [egismoc] ENROLL_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.396: Task SSM done 161s (process:4281): libfprint-device-DEBUG: 03:38:28.396: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 161s (process:4281): libfprint-device-DEBUG: 03:38:28.396: Updated temperature model after 0.09 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.396: List 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.396: [egismoc] LIST_STATES entering state 0 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.396: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.396: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.396: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.397: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.400: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.400: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.400: List callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.401: Device fingerprint 1: FP1-00000000-2-00000000-nobody 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.401: Device fingerprint 2: FP1-00000000-7-00000000-nobody 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.401: Number of currently enrolled fingerprints on the device is 2 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.401: [egismoc] LIST_STATES entering state 1 161s (process:4281): libfprint-device-DEBUG: 03:38:28.401: Device reported listing completion 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.401: [egismoc] LIST_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.401: Task SSM done 161s (process:4281): libfprint-device-DEBUG: 03:38:28.401: Completing action FPI_DEVICE_ACTION_LIST in idle! 161s (process:4281): libfprint-device-DEBUG: 03:38:28.401: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.401: Delete 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.401: [egismoc] DELETE_STATES entering state 0 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.401: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.401: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.401: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.401: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.402: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.402: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.402: List callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.402: Device fingerprint 1: FP1-00000000-2-00000000-nobody 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.402: Device fingerprint 2: FP1-00000000-7-00000000-nobody 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.402: Number of currently enrolled fingerprints on the device is 2 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.402: [egismoc] DELETE_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.402: Get delete command 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.402: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody) 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.402: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.402: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.402: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.403: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.403: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.403: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.403: Delete callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.403: Response prefix valid: yes 161s (process:4281): libfprint-device-DEBUG: 03:38:28.403: Device reported deletion completion 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.403: [egismoc] DELETE_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.403: Task SSM done 161s (process:4281): libfprint-device-DEBUG: 03:38:28.403: Completing action FPI_DEVICE_ACTION_DELETE in idle! 161s (process:4281): libfprint-device-DEBUG: 03:38:28.403: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.403: List 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.403: [egismoc] LIST_STATES entering state 0 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.403: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.403: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.403: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.404: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.404: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.404: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.405: List callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.405: Device fingerprint 1: FP1-00000000-7-00000000-nobody 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.405: Number of currently enrolled fingerprints on the device is 1 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.405: [egismoc] LIST_STATES entering state 1 161s (process:4281): libfprint-device-DEBUG: 03:38:28.405: Device reported listing completion 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.405: [egismoc] LIST_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.405: Task SSM done 161s (process:4281): libfprint-device-DEBUG: 03:38:28.405: Completing action FPI_DEVICE_ACTION_LIST in idle! 161s (process:4281): libfprint-device-DEBUG: 03:38:28.405: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.405: Clear storage 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.405: [egismoc] DELETE_STATES entering state 0 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.405: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.405: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.405: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.405: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.406: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.406: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.406: List callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.406: Device fingerprint 1: FP1-00000000-7-00000000-nobody 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.406: Number of currently enrolled fingerprints on the device is 1 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.406: [egismoc] DELETE_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.406: Get delete command 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.406: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.406: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.406: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.406: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.407: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.407: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.407: Delete callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.407: Response prefix valid: yes 161s (process:4281): libfprint-device-DEBUG: 03:38:28.407: Device reported deletion completion 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.407: [egismoc] DELETE_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.407: Task SSM done 161s (process:4281): libfprint-device-DEBUG: 03:38:28.407: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 161s (process:4281): libfprint-device-DEBUG: 03:38:28.407: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.407: List 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.407: [egismoc] LIST_STATES entering state 0 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.407: Execute command and get response 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.407: Get check bytes 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.407: [egismoc] CMD_STATES entering state 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.408: [egismoc] CMD_STATES entering state 1 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.408: Command receive callback 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.408: [egismoc] CMD_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.408: List callback 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.408: Number of currently enrolled fingerprints on the device is 0 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.408: [egismoc] LIST_STATES entering state 1 161s (process:4281): libfprint-device-DEBUG: 03:38:28.408: Device reported listing completion 161s (process:4281): libfprint-SSM-DEBUG: 03:38:28.408: [egismoc] LIST_STATES completed successfully 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.408: Task SSM done 161s (process:4281): libfprint-device-DEBUG: 03:38:28.408: Completing action FPI_DEVICE_ACTION_LIST in idle! 161s (process:4281): libfprint-device-DEBUG: 03:38:28.408: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.408: Closing device 161s (process:4281): libfprint-egismoc-DEBUG: 03:38:28.408: Cancel 161s (process:4281): libfprint-device-DEBUG: 03:38:28.409: Device reported close completion 161s (process:4281): libfprint-device-DEBUG: 03:38:28.409: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s (process:4281): libfprint-device-DEBUG: 03:38:28.409: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s listing - device should have prints 161s clear device storage 161s clear done 161s listing - device should be empty 161s enrolling 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6fc5dcd0e740 (FpiDeviceEgisMoc at 0x12413250)>, 1, , None, None) 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6fc5dcd0e740 (FpiDeviceEgisMoc at 0x12413250)>, 2, , None, None) 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6fc5dcd0e740 (FpiDeviceEgisMoc at 0x12413250)>, 2, None, None, GLib.Error('Your device is having trouble recognizing you. Make sure your sensor is clean.', 'fp - device - retry - quark', 3)) 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6fc5dcd0e740 (FpiDeviceEgisMoc at 0x12413250)>, 3, , None, None) 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6fc5dcd0e740 (FpiDeviceEgisMoc at 0x12413250)>, 4, , None, None) 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6fc5dcd0e740 (FpiDeviceEgisMoc at 0x12413250)>, 5, , None, None) 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6fc5dcd0e740 (FpiDeviceEgisMoc at 0x12413250)>, 6, , None, None) 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6fc5dcd0e740 (FpiDeviceEgisMoc at 0x12413250)>, 7, , None, None) 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6fc5dcd0e740 (FpiDeviceEgisMoc at 0x12413250)>, 8, , None, None) 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6fc5dcd0e740 (FpiDeviceEgisMoc at 0x12413250)>, 9, , None, None) 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6fc5dcd0e740 (FpiDeviceEgisMoc at 0x12413250)>, 10, , None, None) 161s enroll done 161s listing - device should have 1 print 161s verifying 161s verify done 161s async identifying 161s indentification_done: 161s try to enroll duplicate 161s duplicate enroll attempt done 161s listing - device should still only have 1 print 161s enroll new finger 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6fc5dcd0e740 (FpiDeviceEgisMoc at 0x12413250)>, 1, , None, None) 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6fc5dcd0e740 (FpiDeviceEgisMoc at 0x12413250)>, 2, , None, None) 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6fc5dcd0e740 (FpiDeviceEgisMoc at 0x12413250)>, 2, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6fc5dcd0e740 (FpiDeviceEgisMoc at 0x12413250)>, 2, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6fc5dcd0e740 (FpiDeviceEgisMoc at 0x12413250)>, 3, , None, None) 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6fc5dcd0e740 (FpiDeviceEgisMoc at 0x12413250)>, 3, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6fc5dcd0e740 (FpiDeviceEgisMoc at 0x12413250)>, 4, , None, None) 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6fc5dcd0e740 (FpiDeviceEgisMoc at 0x12413250)>, 5, , None, None) 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6fc5dcd0e740 (FpiDeviceEgisMoc at 0x12413250)>, 6, , None, None) 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6fc5dcd0e740 (FpiDeviceEgisMoc at 0x12413250)>, 7, , None, None) 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6fc5dcd0e740 (FpiDeviceEgisMoc at 0x12413250)>, 8, , None, None) 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6fc5dcd0e740 (FpiDeviceEgisMoc at 0x12413250)>, 9, , None, None) 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6fc5dcd0e740 (FpiDeviceEgisMoc at 0x12413250)>, 10, , None, None) 161s enroll new finger done 161s listing - device should have 2 prints 161s deleting first print 161s delete done 161s listing - device should only have second print 161s clear device storage 161s clear done 161s listing - device should be empty 161s ** (umockdev-run:4277): DEBUG: 03:38:28.421: umockdev.vala:154: Removing test bed /tmp/umockdev.YCU012 161s (umockdev-run:4277): GLib-DEBUG: 03:38:28.428: unsetenv() is not thread-safe and should not be used after threads are created 161s PASS: libfprint-2/driver-egismoc-05a1.test 161s Running test: libfprint-2/driver-elanmoc.test 161s ** (umockdev-run:4289): DEBUG: 03:38:28.470: umockdev.vala:127: Created udev test bed /tmp/umockdev.3NR812 161s ** (umockdev-run:4289): DEBUG: 03:38:28.470: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 161s ** (umockdev-run:4289): DEBUG: 03:38:28.471: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 161s ** (umockdev-run:4289): DEBUG: 03:38:28.475: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3NR812/dev/bus/usb/001/003 161s ** (umockdev-run:4289): DEBUG: 03:38:28.475: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 161s ** (umockdev-run:4289): DEBUG: 03:38:28.476: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 161s ** (umockdev-run:4289): DEBUG: 03:38:28.479: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3NR812/dev/bus/usb/001/001 161s ** (umockdev-run:4289): DEBUG: 03:38:28.479: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 161s ** (umockdev-run:4289): DEBUG: 03:38:28.479: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 161s (process:4293): libfprint-context-DEBUG: 03:38:28.562: Initializing FpContext (libfprint version 1.94.8+tod1) 161s (process:4293): libfprint-tod-DEBUG: 03:38:28.562: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 161s (process:4293): libfprint-elanmoc-DEBUG: 03:38:28.564: 108371794: ../libfprint/drivers/elanmoc/elanmoc.c:1151 161s (process:4293): libfprint-context-DEBUG: 03:38:28.564: No driver found for USB device 1D6B:0002 161s (process:4293): libfprint-device-DEBUG: 03:38:28.564: Device reported probe completion 161s (process:4293): libfprint-device-DEBUG: 03:38:28.564: Completing action FPI_DEVICE_ACTION_PROBE in idle! 161s (process:4293): libfprint-device-DEBUG: 03:38:28.564: Not updating temperature model, device can run continuously! 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.566: [elanmoc] DEV_INIT_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.566: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.566: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.567: [elanmoc] DEV_INIT_STATES entering state 1 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.567: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.568: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.568: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.569: [elanmoc] DEV_INIT_STATES entering state 2 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.569: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.569: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.569: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-elanmoc-DEBUG: 03:38:28.570: elanmoc FW Version 8004 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.570: [elanmoc] DEV_INIT_STATES entering state 3 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.570: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.570: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.571: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-elanmoc-DEBUG: 03:38:28.572: elanmoc last_read DIM 0x57(87) 0x6B(107) 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.572: [elanmoc] DEV_INIT_STATES entering state 4 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.572: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.572: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.573: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-elanmoc-DEBUG: 03:38:28.573: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01) 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.573: [elanmoc] DEV_INIT_STATES completed successfully 161s (process:4293): libfprint-device-DEBUG: 03:38:28.573: Device reported open completion 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.573: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-device-DEBUG: 03:38:28.573: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s (process:4293): libfprint-device-DEBUG: 03:38:28.573: Not updating temperature model, device can run continuously! 161s (process:4293): libfprint-device-DEBUG: 03:38:28.574: Not updating temperature model, device can run continuously! 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.574: [elanmoc] MOC_ENROLL_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.574: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.574: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-elanmoc-DEBUG: 03:38:28.575: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01) 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.575: [elanmoc] MOC_ENROLL_NUM_STATES entering state 1 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.575: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.576: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.576: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-elanmoc-DEBUG: 03:38:28.576: ##### Re-Enrollment Case! ##### 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.576: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.577: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.577: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.577: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-device-DEBUG: 03:38:28.578: Device reported enroll progress, reported 1 of 9 have been completed 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.578: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.578: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.578: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.578: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-device-DEBUG: 03:38:28.579: Device reported enroll progress, reported 2 of 9 have been completed 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.579: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.579: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.579: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.579: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-device-DEBUG: 03:38:28.580: Device reported enroll progress, reported 3 of 9 have been completed 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.580: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.580: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.581: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.581: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-device-DEBUG: 03:38:28.581: Device reported enroll progress, reported 4 of 9 have been completed 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.581: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.581: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.582: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.582: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-device-DEBUG: 03:38:28.582: Device reported enroll progress, reported 5 of 9 have been completed 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.583: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.583: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.583: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.583: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-device-DEBUG: 03:38:28.584: Device reported enroll progress, reported 6 of 9 have been completed 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.584: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.584: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.584: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.584: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-device-DEBUG: 03:38:28.585: Device reported enroll progress, reported 7 of 9 have been completed 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.585: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.585: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.585: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.585: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-device-DEBUG: 03:38:28.586: Device reported enroll progress, reported 7 of 9 have been completed 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.586: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.586: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.586: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.586: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-device-DEBUG: 03:38:28.587: Device reported enroll progress, reported 8 of 9 have been completed 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.587: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.587: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.587: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.587: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-device-DEBUG: 03:38:28.588: Device reported enroll progress, reported 8 of 9 have been completed 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.588: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.588: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.588: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.589: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-device-DEBUG: 03:38:28.589: Device reported enroll progress, reported 9 of 9 have been completed 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.589: [elanmoc] MOC_ENROLL_NUM_STATES entering state 3 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.589: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.590: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.591: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-elanmoc-DEBUG: 03:38:28.591: elanmoc_commit_cb success 161s (process:4293): libfprint-elanmoc-DEBUG: 03:38:28.591: Enrollment was successful! 161s (process:4293): libfprint-device-DEBUG: 03:38:28.591: Device reported enroll completion 161s (process:4293): libfprint-device-DEBUG: 03:38:28.591: Print for finger FP_FINGER_UNKNOWN enrolled 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.591: [elanmoc] MOC_ENROLL_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.591: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-device-DEBUG: 03:38:28.591: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 161s (process:4293): libfprint-device-DEBUG: 03:38:28.591: Not updating temperature model, device can run continuously! 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.591: [elanmoc] MOC_LIST_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.591: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.592: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-elanmoc-DEBUG: 03:38:28.593: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01) 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.593: [elanmoc] MOC_LIST_NUM_STATES entering state 1 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.593: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.593: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.593: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.594: [elanmoc] MOC_LIST_NUM_STATES entering state 1 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.594: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.594: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.594: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.595: [elanmoc] MOC_LIST_NUM_STATES entering state 1 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.595: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.595: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.595: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.596: [elanmoc] MOC_LIST_NUM_STATES entering state 1 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.596: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.596: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.596: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.597: [elanmoc] MOC_LIST_NUM_STATES entering state 1 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.597: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.597: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.598: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.598: [elanmoc] MOC_LIST_NUM_STATES entering state 1 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.598: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.598: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.599: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.599: [elanmoc] MOC_LIST_NUM_STATES entering state 1 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.599: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.599: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.600: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.600: [elanmoc] MOC_LIST_NUM_STATES entering state 1 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.600: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.601: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.601: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.601: [elanmoc] MOC_LIST_NUM_STATES entering state 1 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.601: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.602: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.602: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.603: [elanmoc] MOC_LIST_NUM_STATES entering state 1 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.603: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.603: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.603: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-device-DEBUG: 03:38:28.604: Device reported listing completion 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.604: [elanmoc] MOC_LIST_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.604: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-device-DEBUG: 03:38:28.604: Completing action FPI_DEVICE_ACTION_LIST in idle! 161s (process:4293): libfprint-device-DEBUG: 03:38:28.604: Not updating temperature model, device can run continuously! 161s (process:4293): libfprint-device-DEBUG: 03:38:28.604: Not updating temperature model, device can run continuously! 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.604: [elanmoc] IDENTIFY_NUM_STATES entering state 0 161s (process:4293): libfprint-elanmoc-DEBUG: 03:38:28.604: elanmoc elan_identify_run_state 161s (process:4293): libfprint-elanmoc-DEBUG: 03:38:28.604: elanmoc elan_identify_run_state IDENTIFY_SET_MODE 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.604: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.604: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.605: [elanmoc] IDENTIFY_NUM_STATES entering state 1 161s (process:4293): libfprint-elanmoc-DEBUG: 03:38:28.605: elanmoc elan_identify_run_state 161s (process:4293): libfprint-elanmoc-DEBUG: 03:38:28.605: elanmoc elan_identify_run_state VERIFY_WAIT_FINGER 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.605: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.606: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.606: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-elanmoc-DEBUG: 03:38:28.606: Verify was successful! for user: 0 mesg_code: 1 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.606: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.607: [elanmoc] IDENTIFY_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.607: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.607: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-elanmoc-DEBUG: 03:38:28.607: Verify/Identify successful for: FP1-00000000-0-00000000-nobody 161s (process:4293): libfprint-device-DEBUG: 03:38:28.607: Device reported verify result 161s (process:4293): libfprint-device-DEBUG: 03:38:28.607: Device reported verify completion 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.607: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-device-DEBUG: 03:38:28.607: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 161s (process:4293): libfprint-device-DEBUG: 03:38:28.608: Not updating temperature model, device can run continuously! 161s (process:4293): libfprint-device-DEBUG: 03:38:28.608: Not updating temperature model, device can run continuously! 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.608: [elanmoc] IDENTIFY_NUM_STATES entering state 0 161s (process:4293): libfprint-elanmoc-DEBUG: 03:38:28.608: elanmoc elan_identify_run_state 161s (process:4293): libfprint-elanmoc-DEBUG: 03:38:28.608: elanmoc elan_identify_run_state IDENTIFY_SET_MODE 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.608: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.608: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.609: [elanmoc] IDENTIFY_NUM_STATES entering state 1 161s (process:4293): libfprint-elanmoc-DEBUG: 03:38:28.609: elanmoc elan_identify_run_state 161s (process:4293): libfprint-elanmoc-DEBUG: 03:38:28.609: elanmoc elan_identify_run_state VERIFY_WAIT_FINGER 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.609: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.609: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.610: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-elanmoc-DEBUG: 03:38:28.610: Verify was successful! for user: 0 mesg_code: 1 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.610: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.611: [elanmoc] IDENTIFY_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.611: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.611: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-elanmoc-DEBUG: 03:38:28.611: Verify/Identify successful for: FP1-00000000-0-00000000-nobody 161s (process:4293): libfprint-device-DEBUG: 03:38:28.611: Device reported identify result 161s (process:4293): libfprint-device-DEBUG: 03:38:28.611: Device reported identify completion 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.611: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-device-DEBUG: 03:38:28.611: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 161s (process:4293): libfprint-device-DEBUG: 03:38:28.611: Not updating temperature model, device can run continuously! 161s (process:4293): libfprint-elanmoc-DEBUG: 03:38:28.612: Delete Finger, user_id = FP1-00000000-0-00000000-nobody! 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.612: [elanmoc] DELETE_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.612: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.612: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-device-DEBUG: 03:38:28.613: Device reported deletion completion 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.613: [elanmoc] DELETE_NUM_STATES completed successfully 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.613: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-device-DEBUG: 03:38:28.613: Completing action FPI_DEVICE_ACTION_DELETE in idle! 161s (process:4293): libfprint-device-DEBUG: 03:38:28.613: Not updating temperature model, device can run continuously! 161s (process:4293): libfprint-elanmoc-DEBUG: 03:38:28.613: Elanmoc dev_exit 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.613: [elanmoc] DEV_EXIT_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.613: [elanmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.614: [elanmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.614: [elanmoc] DEV_EXIT_STATES completed successfully 161s (process:4293): libfprint-device-DEBUG: 03:38:28.614: Device reported close completion 161s (process:4293): libfprint-SSM-DEBUG: 03:38:28.614: [elanmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4293): libfprint-device-DEBUG: 03:38:28.614: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s (process:4293): libfprint-device-DEBUG: 03:38:28.614: Not updating temperature model, device can run continuously! 161s enrolling 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x6f77b677b280 (FpiDeviceElanmoc at 0x4d867620)>, 1, None, None, None) 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x6f77b677b280 (FpiDeviceElanmoc at 0x4d867620)>, 2, None, None, None) 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x6f77b677b280 (FpiDeviceElanmoc at 0x4d867620)>, 3, None, None, None) 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x6f77b677b280 (FpiDeviceElanmoc at 0x4d867620)>, 4, None, None, None) 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x6f77b677b280 (FpiDeviceElanmoc at 0x4d867620)>, 5, None, None, None) 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x6f77b677b280 (FpiDeviceElanmoc at 0x4d867620)>, 6, None, None, None) 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x6f77b677b280 (FpiDeviceElanmoc at 0x4d867620)>, 7, None, None, None) 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x6f77b677b280 (FpiDeviceElanmoc at 0x4d867620)>, 7, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x6f77b677b280 (FpiDeviceElanmoc at 0x4d867620)>, 8, None, None, None) 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x6f77b677b280 (FpiDeviceElanmoc at 0x4d867620)>, 8, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 161s finger status: 161s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x6f77b677b280 (FpiDeviceElanmoc at 0x4d867620)>, 9, None, None, None) 161s enroll done 161s listing 161s listing done 161s verifying 161s verify done 161s async identifying 161s indentification_done: 161s deleting 161s delete done 161s ** (umockdev-run:4289): DEBUG: 03:38:28.627: umockdev.vala:154: Removing test bed /tmp/umockdev.3NR812 161s (umockdev-run:4289): GLib-DEBUG: 03:38:28.633: unsetenv() is not thread-safe and should not be used after threads are created 161s PASS: libfprint-2/driver-elanmoc.test 161s Running test: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_current.test 161s TAP version 14 161s # random seed: R02S1fd668e0d22dc2b1f151b8a01adff03c 161s 1..4 161s # Start of context tests 161s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 161s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 161s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x67c4501535d0, GType is 9134124264768 161s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 161s ok 1 /context/new 161s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 161s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 161s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 161s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 161s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 161s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 161s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 161s ok 2 /context/no-devices 161s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 161s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 161s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x67c4501535d0, GType is 9134124264768 161s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 161s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 161s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 161s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 161s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 161s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 161s # libfprint-context-DEBUG: created 161s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 161s # 161s # libfprint-device-DEBUG: Device reported probe completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 161s # 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 161s # 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s ok 3 /context/has-virtual-device 161s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 161s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 161s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x67c4501535d0, GType is 9134124264768 161s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 161s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 161s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 161s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 161s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 161s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 161s # libfprint-context-DEBUG: created 161s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 161s # 161s # libfprint-device-DEBUG: Device reported probe completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s ok 4 /context/enumerates-new-devices 161s # End of context tests 161s PASS: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_current.test 161s Running test: libfprint-2/driver-fpcmoc.test 161s ** (umockdev-run:4313): DEBUG: 03:38:28.702: umockdev.vala:127: Created udev test bed /tmp/umockdev.IWEG22 161s ** (umockdev-run:4313): DEBUG: 03:38:28.702: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-1 161s ** (umockdev-run:4313): DEBUG: 03:38:28.703: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-1 (subsystem usb) 161s ** (umockdev-run:4313): DEBUG: 03:38:28.707: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.IWEG22/dev/bus/usb/001/019 161s ** (umockdev-run:4313): DEBUG: 03:38:28.707: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 161s ** (umockdev-run:4313): DEBUG: 03:38:28.708: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 161s ** (umockdev-run:4313): DEBUG: 03:38:28.712: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.IWEG22/dev/bus/usb/001/001 161s ** (umockdev-run:4313): DEBUG: 03:38:28.712: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 161s ** (umockdev-run:4313): DEBUG: 03:38:28.712: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 161s (process:4317): libfprint-context-DEBUG: 03:38:28.802: Initializing FpContext (libfprint version 1.94.8+tod1) 161s (process:4317): libfprint-tod-DEBUG: 03:38:28.803: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 161s (process:4317): libfprint-DEBUG: 03:38:28.805: fpi_device_fpcmoc_init enter --> 161s (process:4317): libfprint-DEBUG: 03:38:28.805: 108612956: ../libfprint/drivers/fpcmoc/fpc.c:1873 161s (process:4317): libfprint-context-DEBUG: 03:38:28.805: No driver found for USB device 1D6B:0002 161s (process:4317): libfprint-DEBUG: 03:38:28.805: fpc_dev_probe enter --> 161s (process:4317): libfprint-DEBUG: 03:38:28.809: Device name: FPC L:0001 FW:127010 161s (process:4317): libfprint-device-DEBUG: 03:38:28.809: Device reported probe completion 161s (process:4317): libfprint-device-DEBUG: 03:38:28.809: Completing action FPI_DEVICE_ACTION_PROBE in idle! 161s (process:4317): libfprint-device-DEBUG: 03:38:28.809: Not updating temperature model, device can run continuously! 161s (process:4317): libfprint-DEBUG: 03:38:28.810: fpc_dev_open enter --> 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.811: [fpcmoc] FP_INIT_NUM_STATES entering state 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.811: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.811: fpc_send_ctrl_cmd CMD: 0x1, value: 0x1, index: 0 type: 2 161s (process:4317): libfprint-DEBUG: 03:38:28.811: fpc_cmd_receive_cb current ssm request: 1 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.811: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.812: fpc_cmd_receive_cb current ssm request: 1 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.812: fpc_cmd_receive_cb recv evt data length: 38 161s (process:4317): libfprint-DEBUG: 03:38:28.812: fpc_evt_cb INIT: status=0, Sensor = 1523, HWID = 0x1711, WxH = 96 x 96 161s (process:4317): libfprint-DEBUG: 03:38:28.812: fpc_evt_cb INIT: FW version: 1.27.0.10 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.812: [fpcmoc] FP_INIT_NUM_STATES entering state 1 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.812: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.812: fpc_send_ctrl_cmd CMD: 0x60, value: 0x0, index: 0 type: 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.812: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.813: fpc_cmd_receive_cb current ssm request: 96 state: 0 161s (process:4317): libfprint-DEBUG: 03:38:28.813: fpc_init_load_db_cb got dbid size: 16 161s (process:4317): libfprint-DEBUG: 03:38:28.813: fpc_init_load_db_cb dbid: 0xa981b581-adfc-e643-a0d0-88c2138092f7 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.813: [fpcmoc] FP_INIT_NUM_STATES completed successfully 161s (process:4317): libfprint-device-DEBUG: 03:38:28.813: Device reported open completion 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.813: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-device-DEBUG: 03:38:28.813: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s (process:4317): libfprint-device-DEBUG: 03:38:28.813: Not updating temperature model, device can run continuously! 161s (process:4317): libfprint-DEBUG: 03:38:28.813: fpc_dev_clear_storage enter --> 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.813: [fpcmoc] Clear storage entering state 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.813: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.813: fpc_send_ctrl_cmd CMD: 0x62, value: 0x0, index: 0 type: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.813: fpc_cmd_receive_cb current ssm request: 98 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.813: [fpcmoc] Clear storage entering state 1 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.813: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.813: fpc_send_ctrl_cmd CMD: 0x60, value: 0x1, index: 0 type: 1 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.814: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.814: fpc_cmd_receive_cb current ssm request: 96 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.814: [fpcmoc] Clear storage completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.814: Clear Storage complete! 161s (process:4317): libfprint-device-DEBUG: 03:38:28.814: Device reported deletion completion 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.814: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-device-DEBUG: 03:38:28.814: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 161s (process:4317): libfprint-device-DEBUG: 03:38:28.814: Not updating temperature model, device can run continuously! 161s (process:4317): libfprint-device-DEBUG: 03:38:28.815: Not updating temperature model, device can run continuously! 161s (process:4317): libfprint-DEBUG: 03:38:28.815: fpc_dev_enroll enter --> 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.815: [fpcmoc] enroll entering state 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.815: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.815: fpc_send_ctrl_cmd CMD: 0x70, value: 0x0, index: 0 type: 2 161s (process:4317): libfprint-DEBUG: 03:38:28.815: fpc_cmd_receive_cb current ssm request: 112 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.815: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.816: fpc_cmd_receive_cb current ssm request: 112 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.816: fpc_cmd_receive_cb recv evt data length: 790 161s (process:4317): libfprint-DEBUG: 03:38:28.816: fpc_evt_cb Enum Fids: status = 0, NumFids = 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.816: [fpcmoc] enroll entering state 1 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.816: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.816: fpc_send_ctrl_cmd CMD: 0x67, value: 0x0, index: 0 type: 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.816: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.817: fpc_cmd_receive_cb current ssm request: 103 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.817: [fpcmoc] enroll entering state 2 161s (process:4317): libfprint-device-DEBUG: 03:38:28.817: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.817: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.817: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.817: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.818: fpc_cmd_receive_cb current ssm request: 2 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.818: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.818: fpc_cmd_receive_cb current ssm request: 2 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.818: fpc_cmd_receive_cb recv evt data length: 12 161s (process:4317): libfprint-DEBUG: 03:38:28.818: fpc_evt_cb Got finger down event (0) 161s (process:4317): libfprint-device-DEBUG: 03:38:28.818: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.818: [fpcmoc] enroll entering state 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.818: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.818: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.819: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.819: fpc_cmd_receive_cb current ssm request: 9 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.819: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.819: fpc_cmd_receive_cb current ssm request: 9 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.819: fpc_cmd_receive_cb recv evt data length: 24 161s (process:4317): libfprint-DEBUG: 03:38:28.819: fpc_evt_cb Got capture event 161s (process:4317): libfprint-device-DEBUG: 03:38:28.819: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.819: [fpcmoc] enroll entering state 4 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.819: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.819: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.820: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.820: fpc_cmd_receive_cb current ssm request: 104 state: 0 161s (process:4317): libfprint-DEBUG: 03:38:28.820: Enrol Update status: 1, remaining: 11 161s (process:4317): libfprint-device-DEBUG: 03:38:28.820: Device reported enroll progress, reported 1 of 25 have been completed 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.820: [fpcmoc] enroll entering state 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.820: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.820: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.821: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.821: fpc_cmd_receive_cb current ssm request: 2 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.821: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.822: fpc_cmd_receive_cb current ssm request: 2 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.822: fpc_cmd_receive_cb recv evt data length: 12 161s (process:4317): libfprint-DEBUG: 03:38:28.822: fpc_evt_cb Got finger down event (0) 161s (process:4317): libfprint-device-DEBUG: 03:38:28.822: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.822: [fpcmoc] enroll entering state 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.822: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.822: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.822: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.822: fpc_cmd_receive_cb current ssm request: 9 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.822: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.823: fpc_cmd_receive_cb current ssm request: 9 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.823: fpc_cmd_receive_cb recv evt data length: 24 161s (process:4317): libfprint-DEBUG: 03:38:28.823: fpc_evt_cb Got capture event 161s (process:4317): libfprint-device-DEBUG: 03:38:28.823: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.823: [fpcmoc] enroll entering state 4 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.823: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.823: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.823: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.823: fpc_cmd_receive_cb current ssm request: 104 state: 0 161s (process:4317): libfprint-DEBUG: 03:38:28.823: Enrol Update status: 1, remaining: 10 161s (process:4317): libfprint-device-DEBUG: 03:38:28.823: Device reported enroll progress, reported 2 of 25 have been completed 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.824: [fpcmoc] enroll entering state 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.824: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.824: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.824: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.824: fpc_cmd_receive_cb current ssm request: 2 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.824: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.825: fpc_cmd_receive_cb current ssm request: 2 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.825: fpc_cmd_receive_cb recv evt data length: 12 161s (process:4317): libfprint-DEBUG: 03:38:28.825: fpc_evt_cb Got finger down event (0) 161s (process:4317): libfprint-device-DEBUG: 03:38:28.825: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.825: [fpcmoc] enroll entering state 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.825: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.825: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.825: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.826: fpc_cmd_receive_cb current ssm request: 9 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.826: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.826: fpc_cmd_receive_cb current ssm request: 9 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.826: fpc_cmd_receive_cb recv evt data length: 24 161s (process:4317): libfprint-DEBUG: 03:38:28.826: fpc_evt_cb Got capture event 161s (process:4317): libfprint-device-DEBUG: 03:38:28.826: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.826: [fpcmoc] enroll entering state 4 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.826: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.826: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.827: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.827: fpc_cmd_receive_cb current ssm request: 104 state: 0 161s (process:4317): libfprint-DEBUG: 03:38:28.827: Enrol Update status: 1, remaining: 9 161s (process:4317): libfprint-device-DEBUG: 03:38:28.827: Device reported enroll progress, reported 3 of 25 have been completed 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.827: [fpcmoc] enroll entering state 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.827: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.827: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.827: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.827: fpc_cmd_receive_cb current ssm request: 2 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.827: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.828: fpc_cmd_receive_cb current ssm request: 2 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.828: fpc_cmd_receive_cb recv evt data length: 12 161s (process:4317): libfprint-DEBUG: 03:38:28.828: fpc_evt_cb Got finger down event (0) 161s (process:4317): libfprint-device-DEBUG: 03:38:28.828: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.828: [fpcmoc] enroll entering state 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.828: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.828: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.828: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.829: fpc_cmd_receive_cb current ssm request: 9 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.829: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.830: fpc_cmd_receive_cb current ssm request: 9 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.830: fpc_cmd_receive_cb recv evt data length: 24 161s (process:4317): libfprint-DEBUG: 03:38:28.830: fpc_evt_cb Got capture event 161s (process:4317): libfprint-device-DEBUG: 03:38:28.830: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.830: [fpcmoc] enroll entering state 4 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.830: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.830: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.831: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.831: fpc_cmd_receive_cb current ssm request: 104 state: 0 161s (process:4317): libfprint-DEBUG: 03:38:28.831: Enrol Update status: 1, remaining: 8 161s (process:4317): libfprint-device-DEBUG: 03:38:28.831: Device reported enroll progress, reported 4 of 25 have been completed 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.831: [fpcmoc] enroll entering state 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.831: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.831: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.831: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.832: fpc_cmd_receive_cb current ssm request: 2 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.832: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.832: fpc_cmd_receive_cb current ssm request: 2 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.832: fpc_cmd_receive_cb recv evt data length: 12 161s (process:4317): libfprint-DEBUG: 03:38:28.832: fpc_evt_cb Got finger down event (0) 161s (process:4317): libfprint-device-DEBUG: 03:38:28.832: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.832: [fpcmoc] enroll entering state 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.832: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.832: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.833: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.833: fpc_cmd_receive_cb current ssm request: 9 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.833: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.834: fpc_cmd_receive_cb current ssm request: 9 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.834: fpc_cmd_receive_cb recv evt data length: 24 161s (process:4317): libfprint-DEBUG: 03:38:28.834: fpc_evt_cb Got capture event 161s (process:4317): libfprint-device-DEBUG: 03:38:28.834: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.834: [fpcmoc] enroll entering state 4 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.834: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.834: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.835: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.835: fpc_cmd_receive_cb current ssm request: 104 state: 0 161s (process:4317): libfprint-DEBUG: 03:38:28.835: Enrol Update status: 1, remaining: 7 161s (process:4317): libfprint-device-DEBUG: 03:38:28.835: Device reported enroll progress, reported 5 of 25 have been completed 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.835: [fpcmoc] enroll entering state 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.835: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.835: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.836: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.836: fpc_cmd_receive_cb current ssm request: 2 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.836: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.836: fpc_cmd_receive_cb current ssm request: 2 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.837: fpc_cmd_receive_cb recv evt data length: 12 161s (process:4317): libfprint-DEBUG: 03:38:28.837: fpc_evt_cb Got finger down event (0) 161s (process:4317): libfprint-device-DEBUG: 03:38:28.837: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.837: [fpcmoc] enroll entering state 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.837: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.837: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.837: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.837: fpc_cmd_receive_cb current ssm request: 9 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.837: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.838: fpc_cmd_receive_cb current ssm request: 9 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.838: fpc_cmd_receive_cb recv evt data length: 24 161s (process:4317): libfprint-DEBUG: 03:38:28.838: fpc_evt_cb Got capture event 161s (process:4317): libfprint-device-DEBUG: 03:38:28.838: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.838: [fpcmoc] enroll entering state 4 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.838: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.838: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.838: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.839: fpc_cmd_receive_cb current ssm request: 104 state: 0 161s (process:4317): libfprint-DEBUG: 03:38:28.839: Enrol Update status: 5, remaining: 7 161s (process:4317): libfprint-DEBUG: 03:38:28.839: Sample overlapping ratio is too High 161s (process:4317): libfprint-device-DEBUG: 03:38:28.839: Device reported enroll progress, reported 5 of 25 have been completed 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.839: [fpcmoc] enroll entering state 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.839: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.839: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.839: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.839: fpc_cmd_receive_cb current ssm request: 2 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.839: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.840: fpc_cmd_receive_cb current ssm request: 2 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.840: fpc_cmd_receive_cb recv evt data length: 12 161s (process:4317): libfprint-DEBUG: 03:38:28.840: fpc_evt_cb Got finger down event (0) 161s (process:4317): libfprint-device-DEBUG: 03:38:28.840: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.840: [fpcmoc] enroll entering state 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.840: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.840: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.840: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.840: fpc_cmd_receive_cb current ssm request: 9 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.840: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.841: fpc_cmd_receive_cb current ssm request: 9 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.841: fpc_cmd_receive_cb recv evt data length: 24 161s (process:4317): libfprint-DEBUG: 03:38:28.841: fpc_evt_cb Got capture event 161s (process:4317): libfprint-device-DEBUG: 03:38:28.841: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.841: [fpcmoc] enroll entering state 4 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.841: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.841: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.841: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.842: fpc_cmd_receive_cb current ssm request: 104 state: 0 161s (process:4317): libfprint-DEBUG: 03:38:28.842: Enrol Update status: 1, remaining: 6 161s (process:4317): libfprint-device-DEBUG: 03:38:28.842: Device reported enroll progress, reported 6 of 25 have been completed 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.842: [fpcmoc] enroll entering state 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.842: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.842: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.842: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.842: fpc_cmd_receive_cb current ssm request: 2 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.842: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.843: fpc_cmd_receive_cb current ssm request: 2 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.843: fpc_cmd_receive_cb recv evt data length: 12 161s (process:4317): libfprint-DEBUG: 03:38:28.843: fpc_evt_cb Got finger down event (0) 161s (process:4317): libfprint-device-DEBUG: 03:38:28.843: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.843: [fpcmoc] enroll entering state 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.843: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.843: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.843: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.843: fpc_cmd_receive_cb current ssm request: 9 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.843: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.844: fpc_cmd_receive_cb current ssm request: 9 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.844: fpc_cmd_receive_cb recv evt data length: 24 161s (process:4317): libfprint-DEBUG: 03:38:28.844: fpc_evt_cb Got capture event 161s (process:4317): libfprint-device-DEBUG: 03:38:28.844: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.844: [fpcmoc] enroll entering state 4 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.844: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.844: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.844: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.845: fpc_cmd_receive_cb current ssm request: 104 state: 0 161s (process:4317): libfprint-DEBUG: 03:38:28.845: Enrol Update status: 1, remaining: 5 161s (process:4317): libfprint-device-DEBUG: 03:38:28.845: Device reported enroll progress, reported 7 of 25 have been completed 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.845: [fpcmoc] enroll entering state 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.845: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.845: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.845: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.845: fpc_cmd_receive_cb current ssm request: 2 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.845: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.846: fpc_cmd_receive_cb current ssm request: 2 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.846: fpc_cmd_receive_cb recv evt data length: 12 161s (process:4317): libfprint-DEBUG: 03:38:28.846: fpc_evt_cb Got finger down event (0) 161s (process:4317): libfprint-device-DEBUG: 03:38:28.846: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.846: [fpcmoc] enroll entering state 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.846: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.846: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.846: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.846: fpc_cmd_receive_cb current ssm request: 9 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.846: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.847: fpc_cmd_receive_cb current ssm request: 9 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.847: fpc_cmd_receive_cb recv evt data length: 24 161s (process:4317): libfprint-DEBUG: 03:38:28.847: fpc_evt_cb Got capture event 161s (process:4317): libfprint-device-DEBUG: 03:38:28.847: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.847: [fpcmoc] enroll entering state 4 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.847: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.847: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.847: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.848: fpc_cmd_receive_cb current ssm request: 104 state: 0 161s (process:4317): libfprint-DEBUG: 03:38:28.848: Enrol Update status: 5, remaining: 5 161s (process:4317): libfprint-DEBUG: 03:38:28.848: Sample overlapping ratio is too High 161s (process:4317): libfprint-device-DEBUG: 03:38:28.848: Device reported enroll progress, reported 7 of 25 have been completed 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.848: [fpcmoc] enroll entering state 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.848: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.848: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.848: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.848: fpc_cmd_receive_cb current ssm request: 2 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.848: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.849: fpc_cmd_receive_cb current ssm request: 2 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.849: fpc_cmd_receive_cb recv evt data length: 12 161s (process:4317): libfprint-DEBUG: 03:38:28.849: fpc_evt_cb Got finger down event (0) 161s (process:4317): libfprint-device-DEBUG: 03:38:28.849: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.849: [fpcmoc] enroll entering state 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.849: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.849: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.849: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.849: fpc_cmd_receive_cb current ssm request: 9 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.849: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.850: fpc_cmd_receive_cb current ssm request: 9 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.850: fpc_cmd_receive_cb recv evt data length: 24 161s (process:4317): libfprint-DEBUG: 03:38:28.850: fpc_evt_cb Got capture event 161s (process:4317): libfprint-device-DEBUG: 03:38:28.850: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.850: [fpcmoc] enroll entering state 4 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.850: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.850: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.850: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.850: fpc_cmd_receive_cb current ssm request: 104 state: 0 161s (process:4317): libfprint-DEBUG: 03:38:28.851: Enrol Update status: 1, remaining: 4 161s (process:4317): libfprint-device-DEBUG: 03:38:28.851: Device reported enroll progress, reported 8 of 25 have been completed 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.851: [fpcmoc] enroll entering state 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.851: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.851: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.851: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.851: fpc_cmd_receive_cb current ssm request: 2 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.851: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.852: fpc_cmd_receive_cb current ssm request: 2 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.852: fpc_cmd_receive_cb recv evt data length: 12 161s (process:4317): libfprint-DEBUG: 03:38:28.852: fpc_evt_cb Got finger down event (0) 161s (process:4317): libfprint-device-DEBUG: 03:38:28.852: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.852: [fpcmoc] enroll entering state 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.852: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.852: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.852: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.852: fpc_cmd_receive_cb current ssm request: 9 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.852: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.853: fpc_cmd_receive_cb current ssm request: 9 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.853: fpc_cmd_receive_cb recv evt data length: 24 161s (process:4317): libfprint-DEBUG: 03:38:28.853: fpc_evt_cb Got capture event 161s (process:4317): libfprint-device-DEBUG: 03:38:28.853: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.853: [fpcmoc] enroll entering state 4 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.853: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.853: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.853: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.853: fpc_cmd_receive_cb current ssm request: 104 state: 0 161s (process:4317): libfprint-DEBUG: 03:38:28.853: Enrol Update status: 1, remaining: 3 161s (process:4317): libfprint-device-DEBUG: 03:38:28.853: Device reported enroll progress, reported 9 of 25 have been completed 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.853: [fpcmoc] enroll entering state 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.853: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.853: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.854: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.854: fpc_cmd_receive_cb current ssm request: 2 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.854: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.855: fpc_cmd_receive_cb current ssm request: 2 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.855: fpc_cmd_receive_cb recv evt data length: 12 161s (process:4317): libfprint-DEBUG: 03:38:28.855: fpc_evt_cb Got finger down event (0) 161s (process:4317): libfprint-device-DEBUG: 03:38:28.855: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.855: [fpcmoc] enroll entering state 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.855: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.855: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.855: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.855: fpc_cmd_receive_cb current ssm request: 9 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.855: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.856: fpc_cmd_receive_cb current ssm request: 9 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.856: fpc_cmd_receive_cb recv evt data length: 24 161s (process:4317): libfprint-DEBUG: 03:38:28.856: fpc_evt_cb Got capture event 161s (process:4317): libfprint-device-DEBUG: 03:38:28.856: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.856: [fpcmoc] enroll entering state 4 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.856: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.856: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.856: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.856: fpc_cmd_receive_cb current ssm request: 104 state: 0 161s (process:4317): libfprint-DEBUG: 03:38:28.856: Enrol Update status: 1, remaining: 2 161s (process:4317): libfprint-device-DEBUG: 03:38:28.856: Device reported enroll progress, reported 10 of 25 have been completed 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.856: [fpcmoc] enroll entering state 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.856: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.856: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.857: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.857: fpc_cmd_receive_cb current ssm request: 2 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.857: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.858: fpc_cmd_receive_cb current ssm request: 2 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.858: fpc_cmd_receive_cb recv evt data length: 12 161s (process:4317): libfprint-DEBUG: 03:38:28.858: fpc_evt_cb Got finger down event (0) 161s (process:4317): libfprint-device-DEBUG: 03:38:28.858: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.858: [fpcmoc] enroll entering state 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.858: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.858: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.858: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.858: fpc_cmd_receive_cb current ssm request: 9 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.858: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.859: fpc_cmd_receive_cb current ssm request: 9 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.859: fpc_cmd_receive_cb recv evt data length: 24 161s (process:4317): libfprint-DEBUG: 03:38:28.859: fpc_evt_cb Got capture event 161s (process:4317): libfprint-device-DEBUG: 03:38:28.859: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.859: [fpcmoc] enroll entering state 4 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.859: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.859: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.859: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.859: fpc_cmd_receive_cb current ssm request: 104 state: 0 161s (process:4317): libfprint-DEBUG: 03:38:28.860: Enrol Update status: 5, remaining: 2 161s (process:4317): libfprint-DEBUG: 03:38:28.860: Sample overlapping ratio is too High 161s (process:4317): libfprint-device-DEBUG: 03:38:28.860: Device reported enroll progress, reported 10 of 25 have been completed 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.860: [fpcmoc] enroll entering state 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.860: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.860: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.860: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.860: fpc_cmd_receive_cb current ssm request: 2 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.860: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.861: fpc_cmd_receive_cb current ssm request: 2 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.861: fpc_cmd_receive_cb recv evt data length: 12 161s (process:4317): libfprint-DEBUG: 03:38:28.861: fpc_evt_cb Got finger down event (0) 161s (process:4317): libfprint-device-DEBUG: 03:38:28.861: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.861: [fpcmoc] enroll entering state 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.861: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.861: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.861: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.861: fpc_cmd_receive_cb current ssm request: 9 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.861: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.862: fpc_cmd_receive_cb current ssm request: 9 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.862: fpc_cmd_receive_cb recv evt data length: 24 161s (process:4317): libfprint-DEBUG: 03:38:28.862: fpc_evt_cb Got capture event 161s (process:4317): libfprint-device-DEBUG: 03:38:28.862: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.862: [fpcmoc] enroll entering state 4 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.862: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.862: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.862: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.863: fpc_cmd_receive_cb current ssm request: 104 state: 0 161s (process:4317): libfprint-DEBUG: 03:38:28.863: Enrol Update status: 1, remaining: 1 161s (process:4317): libfprint-device-DEBUG: 03:38:28.863: Device reported enroll progress, reported 11 of 25 have been completed 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.863: [fpcmoc] enroll entering state 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.863: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.863: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.863: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.863: fpc_cmd_receive_cb current ssm request: 2 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.863: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.864: fpc_cmd_receive_cb current ssm request: 2 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.864: fpc_cmd_receive_cb recv evt data length: 12 161s (process:4317): libfprint-DEBUG: 03:38:28.864: fpc_evt_cb Got finger down event (0) 161s (process:4317): libfprint-device-DEBUG: 03:38:28.864: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.864: [fpcmoc] enroll entering state 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.864: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.864: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.864: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.864: fpc_cmd_receive_cb current ssm request: 9 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.864: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.865: fpc_cmd_receive_cb current ssm request: 9 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.865: fpc_cmd_receive_cb recv evt data length: 24 161s (process:4317): libfprint-DEBUG: 03:38:28.865: fpc_evt_cb Got capture event 161s (process:4317): libfprint-device-DEBUG: 03:38:28.865: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.865: [fpcmoc] enroll entering state 4 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.865: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.865: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.865: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.865: fpc_cmd_receive_cb current ssm request: 104 state: 0 161s (process:4317): libfprint-DEBUG: 03:38:28.865: Enrol Update status: 0, remaining: 0 161s (process:4317): libfprint-device-DEBUG: 03:38:28.865: Device reported enroll progress, reported 12 of 25 have been completed 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.866: [fpcmoc] enroll entering state 5 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.866: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.866: fpc_send_ctrl_cmd CMD: 0x69, value: 0x0, index: 0 type: 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.866: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.866: fpc_cmd_receive_cb current ssm request: 105 state: 0 161s (process:4317): libfprint-DEBUG: 03:38:28.866: Enrol End status: 0, fid: 0x0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.866: [fpcmoc] enroll entering state 6 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.866: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.866: fpc_send_ctrl_cmd CMD: 0x6b, value: 0x0, index: 0 type: 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.866: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.867: fpc_cmd_receive_cb current ssm request: 107 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.867: [fpcmoc] enroll entering state 7 161s (process:4317): libfprint-DEBUG: 03:38:28.867: user_id: FP1-00000000-0-00000000-nobody, finger: 0xf5 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.867: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.867: fpc_send_ctrl_cmd CMD: 0x6a, value: 0x0, index: 0 type: 1 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.867: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.868: fpc_cmd_receive_cb current ssm request: 106 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.868: [fpcmoc] enroll entering state 8 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.868: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.868: fpc_send_ctrl_cmd CMD: 0x61, value: 0x0, index: 0 type: 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.868: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.868: fpc_cmd_receive_cb current ssm request: 97 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.868: [fpcmoc] enroll entering state 9 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.868: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.868: fpc_send_ctrl_cmd CMD: 0x3, value: 0x1, index: 0 type: 1 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.869: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.869: fpc_cmd_receive_cb current ssm request: 3 state: 0 161s (process:4317): libfprint-DEBUG: 03:38:28.869: fpc_do_abort_cb Do abort for reasons 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.869: [fpcmoc] enroll entering state 10 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.869: [fpcmoc] enroll completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.869: Enrollment complete! 161s (process:4317): libfprint-device-DEBUG: 03:38:28.869: Device reported enroll completion 161s (process:4317): libfprint-device-DEBUG: 03:38:28.869: Device reported finger status change: FP_FINGER_STATUS_NONE 161s (process:4317): libfprint-device-DEBUG: 03:38:28.869: Print for finger FP_FINGER_UNKNOWN enrolled 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.869: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-device-DEBUG: 03:38:28.869: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 161s (process:4317): libfprint-device-DEBUG: 03:38:28.869: Not updating temperature model, device can run continuously! 161s (process:4317): libfprint-DEBUG: 03:38:28.869: fpc_dev_template_list enter --> 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.869: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.869: fpc_send_ctrl_cmd CMD: 0x70, value: 0x0, index: 0 type: 2 161s (process:4317): libfprint-DEBUG: 03:38:28.869: fpc_cmd_receive_cb current ssm request: 112 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.870: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.870: fpc_cmd_receive_cb current ssm request: 112 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.870: fpc_cmd_receive_cb recv evt data length: 790 161s (process:4317): libfprint-DEBUG: 03:38:28.870: Query templates complete! 161s (process:4317): libfprint-device-DEBUG: 03:38:28.870: Device reported listing completion 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.870: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-device-DEBUG: 03:38:28.870: Completing action FPI_DEVICE_ACTION_LIST in idle! 161s (process:4317): libfprint-device-DEBUG: 03:38:28.870: Not updating temperature model, device can run continuously! 161s (process:4317): libfprint-device-DEBUG: 03:38:28.871: Not updating temperature model, device can run continuously! 161s (process:4317): libfprint-DEBUG: 03:38:28.871: fpc_dev_verify_identify enter --> 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.871: [fpcmoc] verify_identify entering state 0 161s (process:4317): libfprint-device-DEBUG: 03:38:28.871: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.871: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.871: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 161s (process:4317): libfprint-DEBUG: 03:38:28.871: fpc_cmd_receive_cb current ssm request: 2 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.871: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.872: fpc_cmd_receive_cb current ssm request: 2 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.872: fpc_cmd_receive_cb recv evt data length: 12 161s (process:4317): libfprint-DEBUG: 03:38:28.872: fpc_evt_cb Got finger down event (0) 161s (process:4317): libfprint-device-DEBUG: 03:38:28.872: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.872: [fpcmoc] verify_identify entering state 1 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.872: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.872: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.872: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.872: fpc_cmd_receive_cb current ssm request: 9 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.872: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.873: fpc_cmd_receive_cb current ssm request: 9 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.873: fpc_cmd_receive_cb recv evt data length: 24 161s (process:4317): libfprint-DEBUG: 03:38:28.873: fpc_evt_cb Got capture event 161s (process:4317): libfprint-device-DEBUG: 03:38:28.873: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.873: [fpcmoc] verify_identify entering state 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.873: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.873: fpc_send_ctrl_cmd CMD: 0x6b, value: 0x0, index: 0 type: 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.873: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.874: fpc_cmd_receive_cb current ssm request: 107 state: 0 161s (process:4317): libfprint-device-DEBUG: 03:38:28.874: Device reported verify result 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.874: [fpcmoc] verify_identify entering state 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.874: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.874: fpc_send_ctrl_cmd CMD: 0x3, value: 0x1, index: 0 type: 1 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.874: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.874: fpc_cmd_receive_cb current ssm request: 3 state: 0 161s (process:4317): libfprint-DEBUG: 03:38:28.874: fpc_do_abort_cb Do abort for reasons 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.874: [fpcmoc] verify_identify completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.874: Verify_identify complete! 161s (process:4317): libfprint-device-DEBUG: 03:38:28.874: Device reported verify completion 161s (process:4317): libfprint-device-DEBUG: 03:38:28.874: Device reported finger status change: FP_FINGER_STATUS_NONE 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.874: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-device-DEBUG: 03:38:28.874: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 161s (process:4317): libfprint-device-DEBUG: 03:38:28.874: Not updating temperature model, device can run continuously! 161s (process:4317): libfprint-device-DEBUG: 03:38:28.875: Not updating temperature model, device can run continuously! 161s (process:4317): libfprint-DEBUG: 03:38:28.875: fpc_dev_verify_identify enter --> 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.875: [fpcmoc] verify_identify entering state 0 161s (process:4317): libfprint-device-DEBUG: 03:38:28.875: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.875: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.875: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 161s (process:4317): libfprint-DEBUG: 03:38:28.876: fpc_cmd_receive_cb current ssm request: 2 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.876: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.876: fpc_cmd_receive_cb current ssm request: 2 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.876: fpc_cmd_receive_cb recv evt data length: 12 161s (process:4317): libfprint-DEBUG: 03:38:28.876: fpc_evt_cb Got finger down event (0) 161s (process:4317): libfprint-device-DEBUG: 03:38:28.876: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.876: [fpcmoc] verify_identify entering state 1 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.876: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.877: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.877: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.877: fpc_cmd_receive_cb current ssm request: 9 state: 0 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.877: [fpcmoc] FP_CMD_NUM_STATES entering state 1 161s (process:4317): libfprint-DEBUG: 03:38:28.878: fpc_cmd_receive_cb current ssm request: 9 state: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.878: fpc_cmd_receive_cb recv evt data length: 24 161s (process:4317): libfprint-DEBUG: 03:38:28.878: fpc_evt_cb Got capture event 161s (process:4317): libfprint-device-DEBUG: 03:38:28.878: Device reported finger status change: FP_FINGER_STATUS_NEEDED 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.878: [fpcmoc] verify_identify entering state 2 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.878: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.878: fpc_send_ctrl_cmd CMD: 0x6b, value: 0x0, index: 0 type: 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.878: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.878: fpc_cmd_receive_cb current ssm request: 107 state: 0 161s (process:4317): libfprint-device-DEBUG: 03:38:28.878: Device reported identify result 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.878: [fpcmoc] verify_identify entering state 3 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.878: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.878: fpc_send_ctrl_cmd CMD: 0x3, value: 0x1, index: 0 type: 1 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.879: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.879: fpc_cmd_receive_cb current ssm request: 3 state: 0 161s (process:4317): libfprint-DEBUG: 03:38:28.879: fpc_do_abort_cb Do abort for reasons 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.879: [fpcmoc] verify_identify completed successfully 161s (process:4317): libfprint-DEBUG: 03:38:28.879: Verify_identify complete! 161s (process:4317): libfprint-device-DEBUG: 03:38:28.879: Device reported identify completion 161s (process:4317): libfprint-device-DEBUG: 03:38:28.879: Device reported finger status change: FP_FINGER_STATUS_NONE 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.879: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-device-DEBUG: 03:38:28.879: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 161s (process:4317): libfprint-device-DEBUG: 03:38:28.879: Not updating temperature model, device can run continuously! 161s (process:4317): libfprint-DEBUG: 03:38:28.880: fpc_dev_template_delete enter --> 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.880: [fpcmoc] FP_CMD_NUM_STATES entering state 0 161s (process:4317): libfprint-DEBUG: 03:38:28.880: fpc_send_ctrl_cmd CMD: 0x63, value: 0x0, index: 0 type: 1 161s (process:4317): libfprint-DEBUG: 03:38:28.880: fpc_dev_template_delete exit <-- 161s (process:4317): libfprint-DEBUG: 03:38:28.880: fpc_cmd_receive_cb current ssm request: 99 state: 0 161s (process:4317): libfprint-device-DEBUG: 03:38:28.880: Device reported deletion completion 161s (process:4317): libfprint-SSM-DEBUG: 03:38:28.880: [fpcmoc] FP_CMD_NUM_STATES completed successfully 161s (process:4317): libfprint-device-DEBUG: 03:38:28.880: Completing action FPI_DEVICE_ACTION_DELETE in idle! 161s (process:4317): libfprint-device-DEBUG: 03:38:28.880: Not updating temperature model, device can run continuously! 161s (process:4317): libfprint-DEBUG: 03:38:28.881: fpc_dev_close enter --> 161s (process:4317): libfprint-device-DEBUG: 03:38:28.881: Device reported close completion 161s (process:4317): libfprint-device-DEBUG: 03:38:28.881: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s (process:4317): libfprint-device-DEBUG: 03:38:28.881: Not updating temperature model, device can run continuously! 161s Clear 161s Clear done 161s enrolling 161s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x601cf4289d40 (FpiDeviceFpcMoc at 0x12cbb060)>, 1, None, None, None) 161s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x601cf4289d40 (FpiDeviceFpcMoc at 0x12cbb060)>, 2, None, None, None) 161s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x601cf4289d40 (FpiDeviceFpcMoc at 0x12cbb060)>, 3, None, None, None) 161s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x601cf4289d40 (FpiDeviceFpcMoc at 0x12cbb060)>, 4, None, None, None) 161s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x601cf4289d40 (FpiDeviceFpcMoc at 0x12cbb060)>, 5, None, None, None) 161s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x601cf4289d40 (FpiDeviceFpcMoc at 0x12cbb060)>, 5, None, None, GLib.Error('Please try again after removing the finger first.', 'fp - device - retry - quark', 3)) 161s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x601cf4289d40 (FpiDeviceFpcMoc at 0x12cbb060)>, 6, None, None, None) 161s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x601cf4289d40 (FpiDeviceFpcMoc at 0x12cbb060)>, 7, None, None, None) 161s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x601cf4289d40 (FpiDeviceFpcMoc at 0x12cbb060)>, 7, None, None, GLib.Error('Please try again after removing the finger first.', 'fp - device - retry - quark', 3)) 161s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x601cf4289d40 (FpiDeviceFpcMoc at 0x12cbb060)>, 8, None, None, None) 161s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x601cf4289d40 (FpiDeviceFpcMoc at 0x12cbb060)>, 9, None, None, None) 161s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x601cf4289d40 (FpiDeviceFpcMoc at 0x12cbb060)>, 10, None, None, None) 161s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x601cf4289d40 (FpiDeviceFpcMoc at 0x12cbb060)>, 10, None, None, GLib.Error('Please try again after removing the finger first.', 'fp - device - retry - quark', 3)) 161s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x601cf4289d40 (FpiDeviceFpcMoc at 0x12cbb060)>, 11, None, None, None) 161s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x601cf4289d40 (FpiDeviceFpcMoc at 0x12cbb060)>, 12, None, None, None) 161s enroll done 161s listing 161s listing done 161s verifying 161s verify done 161s async identifying 161s indentification_done: 161s deleting 161s delete done 161s ** (umockdev-run:4313): DEBUG: 03:38:28.894: umockdev.vala:154: Removing test bed /tmp/umockdev.IWEG22 161s (umockdev-run:4313): GLib-DEBUG: 03:38:28.900: unsetenv() is not thread-safe and should not be used after threads are created 161s PASS: libfprint-2/driver-fpcmoc.test 161s Running test: libfprint-2/driver-egismoc.test 161s ** (umockdev-run:4325): DEBUG: 03:38:28.945: umockdev.vala:127: Created udev test bed /tmp/umockdev.L41K22 161s ** (umockdev-run:4325): DEBUG: 03:38:28.945: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3/3-5 161s ** (umockdev-run:4325): DEBUG: 03:38:28.947: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3/3-5 (subsystem usb) 161s ** (umockdev-run:4325): DEBUG: 03:38:28.951: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.L41K22/dev/bus/usb/003/012 161s ** (umockdev-run:4325): DEBUG: 03:38:28.951: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3 161s ** (umockdev-run:4325): DEBUG: 03:38:28.952: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3 (subsystem usb) 161s ** (umockdev-run:4325): DEBUG: 03:38:28.955: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.L41K22/dev/bus/usb/003/001 161s ** (umockdev-run:4325): DEBUG: 03:38:28.955: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 161s ** (umockdev-run:4325): DEBUG: 03:38:28.956: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 162s (process:4329): libfprint-context-DEBUG: 03:38:29.041: Initializing FpContext (libfprint version 1.94.8+tod1) 162s (process:4329): libfprint-tod-DEBUG: 03:38:29.041: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.043: 108850914: ../libfprint/drivers/egismoc/egismoc.c:1597 162s (process:4329): libfprint-context-DEBUG: 03:38:29.043: No driver found for USB device 1D6B:0002 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.043: egismoc_probe enter --> 162s (process:4329): libfprint-device-DEBUG: 03:38:29.045: Device reported probe completion 162s (process:4329): libfprint-device-DEBUG: 03:38:29.046: Completing action FPI_DEVICE_ACTION_PROBE in idle! 162s (process:4329): libfprint-device-DEBUG: 03:38:29.046: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.046: Opening device 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.047: [egismoc] DEV_INIT_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.048: [egismoc] DEV_INIT_STATES entering state 1 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.048: [egismoc] DEV_INIT_STATES entering state 2 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.049: [egismoc] DEV_INIT_STATES entering state 3 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.050: [egismoc] DEV_INIT_STATES entering state 4 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.050: [egismoc] DEV_INIT_STATES entering state 5 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.050: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.050: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.051: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.051: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.052: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.052: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.052: Firmware version callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.052: Response suffix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.052: Device firmware version is 9050.1.1.81 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.052: [egismoc] DEV_INIT_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.052: Task SSM done 162s (process:4329): libfprint-device-DEBUG: 03:38:29.052: Device reported open completion 162s (process:4329): libfprint-device-DEBUG: 03:38:29.052: Completing action FPI_DEVICE_ACTION_OPEN in idle! 162s (process:4329): libfprint-device-DEBUG: 03:38:29.052: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.053: List 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.053: [egismoc] LIST_STATES entering state 0 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.053: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.053: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.053: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.053: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.054: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.054: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.054: List callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.054: Device fingerprint 1: FP1-20231016-1-AAA9163E-root 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.054: Device fingerprint 2: FP1-20231016-2-5102A0A3-root 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.054: Device fingerprint 3: FP1-20231016-3-5159A026-root 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.054: Device fingerprint 4: FP1-20231016-4-A25C1212-root 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.054: Device fingerprint 5: FP1-20231016-5-EC893AA9-root 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.054: Device fingerprint 6: \u0006\u001d\xcbc$ir%\xa22U֨\o\xff\x8ddY\x84\u0003\xbac\xcfO\xde\xc2!L\u001eN( 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.055: Device fingerprint 7: \xd7pܖsT3\xf6>\xd9\u0002"/[\xf8\u0017Iqpz\u000c\xfa,M\xdfm5\u007fq\xc6\xdew 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.055: Number of currently enrolled fingerprints on the device is 7 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.055: [egismoc] LIST_STATES entering state 1 162s (process:4329): libfprint-device-DEBUG: 03:38:29.055: Device reported listing completion 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.055: [egismoc] LIST_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.055: Task SSM done 162s (process:4329): libfprint-device-DEBUG: 03:38:29.055: Completing action FPI_DEVICE_ACTION_LIST in idle! 162s (process:4329): libfprint-device-DEBUG: 03:38:29.055: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.055: Clear storage 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.055: [egismoc] DELETE_STATES entering state 0 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.055: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.055: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.055: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.055: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.057: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.057: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.057: List callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.057: Device fingerprint 1: FP1-20231016-1-AAA9163E-root 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.057: Device fingerprint 2: FP1-20231016-2-5102A0A3-root 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.057: Device fingerprint 3: FP1-20231016-3-5159A026-root 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.057: Device fingerprint 4: FP1-20231016-4-A25C1212-root 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.057: Device fingerprint 5: FP1-20231016-5-EC893AA9-root 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.057: Device fingerprint 6: \u0006\u001d\xcbc$ir%\xa22U֨\o\xff\x8ddY\x84\u0003\xbac\xcfO\xde\xc2!L\u001eN( 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.057: Device fingerprint 7: \xd7pܖsT3\xf6>\xd9\u0002"/[\xf8\u0017Iqpz\u000c\xfa,M\xdfm5\u007fq\xc6\xdew 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.057: Number of currently enrolled fingerprints on the device is 7 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.057: [egismoc] DELETE_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.057: Get delete command 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.057: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.057: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.057: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.058: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.058: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.058: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.058: Delete callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.058: Response prefix valid: yes 162s (process:4329): libfprint-device-DEBUG: 03:38:29.058: Device reported deletion completion 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.058: [egismoc] DELETE_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.058: Task SSM done 162s (process:4329): libfprint-device-DEBUG: 03:38:29.058: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 162s (process:4329): libfprint-device-DEBUG: 03:38:29.058: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.058: List 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.058: [egismoc] LIST_STATES entering state 0 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.058: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.058: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.058: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.059: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.060: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.060: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.060: List callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.060: Number of currently enrolled fingerprints on the device is 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.060: [egismoc] LIST_STATES entering state 1 162s (process:4329): libfprint-device-DEBUG: 03:38:29.060: Device reported listing completion 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.060: [egismoc] LIST_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.060: Task SSM done 162s (process:4329): libfprint-device-DEBUG: 03:38:29.060: Completing action FPI_DEVICE_ACTION_LIST in idle! 162s (process:4329): libfprint-device-DEBUG: 03:38:29.060: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 162s (process:4329): libfprint-device-DEBUG: 03:38:29.060: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.060: Enroll 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.060: [egismoc] ENROLL_STATES entering state 0 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.060: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.060: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.060: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.061: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.062: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.062: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.062: List callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.062: Number of currently enrolled fingerprints on the device is 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.062: [egismoc] ENROLL_STATES entering state 1 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.062: [egismoc] ENROLL_STATES entering state 2 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.062: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.062: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.062: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.063: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.063: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.063: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.063: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.063: [egismoc] ENROLL_STATES entering state 3 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.063: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.063: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.063: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.064: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.064: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.064: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.064: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.064: [egismoc] ENROLL_STATES entering state 4 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.064: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.064: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.065: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.065: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.065: [egismoc] ENROLL_STATES entering state 5 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.065: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.065: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.065: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.066: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.066: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.066: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.066: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.066: [egismoc] ENROLL_STATES entering state 6 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.066: Get check command 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.066: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.066: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.066: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.067: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.067: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.067: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.067: Enroll check callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.067: Response suffix valid: yes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.067: [egismoc] ENROLL_STATES entering state 7 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.067: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.067: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.067: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.068: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.069: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.069: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.069: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.069: [egismoc] ENROLL_STATES entering state 8 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.069: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.069: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.069: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.069: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.070: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.070: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.070: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.070: [egismoc] ENROLL_STATES entering state 9 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.070: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.070: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.070: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.070: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.071: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.071: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.071: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.071: [egismoc] ENROLL_STATES entering state 10 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.071: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.071: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.071: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.071: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.071: [egismoc] ENROLL_STATES entering state 11 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.071: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.071: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.071: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.072: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.073: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.073: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.073: Read capture callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.073: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.073: Response suffix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.073: Partial capture successful. Please touch the sensor again (1/10) 162s (process:4329): libfprint-device-DEBUG: 03:38:29.073: Device reported enroll progress, reported 1 of 10 have been completed 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.073: [egismoc] ENROLL_STATES entering state 8 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.073: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.073: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.073: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.073: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.074: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.074: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.074: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.074: [egismoc] ENROLL_STATES entering state 9 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.074: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.074: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.074: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.075: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.075: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.075: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.075: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.075: [egismoc] ENROLL_STATES entering state 10 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.075: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.075: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.076: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.076: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.076: [egismoc] ENROLL_STATES entering state 11 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.076: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.076: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.076: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.076: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.077: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.077: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.077: Read capture callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.077: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.077: Response suffix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.077: Partial capture successful. Please touch the sensor again (2/10) 162s (process:4329): libfprint-device-DEBUG: 03:38:29.077: Device reported enroll progress, reported 2 of 10 have been completed 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.077: [egismoc] ENROLL_STATES entering state 8 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.077: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.077: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.077: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.078: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.078: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.078: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.078: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.078: [egismoc] ENROLL_STATES entering state 9 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.078: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.078: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.078: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.079: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.079: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.079: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.079: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.079: [egismoc] ENROLL_STATES entering state 10 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.079: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.079: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.080: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.080: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.080: [egismoc] ENROLL_STATES entering state 11 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.080: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.080: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.080: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.081: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.081: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.081: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.081: Read capture callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.081: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.081: Response suffix valid: NO 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.081: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.081: Response suffix valid: yes 162s (process:4329): libfprint-device-DEBUG: 03:38:29.081: Device reported enroll progress, reported 2 of 10 have been completed 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.081: [egismoc] ENROLL_STATES entering state 8 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.081: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.081: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.081: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.082: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.082: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.083: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.083: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.083: [egismoc] ENROLL_STATES entering state 9 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.083: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.083: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.083: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.083: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.084: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.084: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.084: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.084: [egismoc] ENROLL_STATES entering state 10 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.084: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.084: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.084: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.084: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.085: [egismoc] ENROLL_STATES entering state 11 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.085: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.085: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.085: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.085: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.086: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.086: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.086: Read capture callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.086: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.086: Response suffix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.086: Partial capture successful. Please touch the sensor again (3/10) 162s (process:4329): libfprint-device-DEBUG: 03:38:29.086: Device reported enroll progress, reported 3 of 10 have been completed 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.086: [egismoc] ENROLL_STATES entering state 8 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.086: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.086: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.086: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.086: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.087: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.087: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.087: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.087: [egismoc] ENROLL_STATES entering state 9 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.087: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.087: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.087: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.088: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.089: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.089: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.089: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.089: [egismoc] ENROLL_STATES entering state 10 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.089: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.089: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.090: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.090: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.090: [egismoc] ENROLL_STATES entering state 11 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.090: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.090: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.090: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.090: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.091: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.091: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.091: Read capture callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.091: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.091: Response suffix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.091: Partial capture successful. Please touch the sensor again (4/10) 162s (process:4329): libfprint-device-DEBUG: 03:38:29.091: Device reported enroll progress, reported 4 of 10 have been completed 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.091: [egismoc] ENROLL_STATES entering state 8 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.091: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.091: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.091: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.092: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.093: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.093: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.093: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.093: [egismoc] ENROLL_STATES entering state 9 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.093: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.093: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.093: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.093: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.094: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.094: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.094: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.094: [egismoc] ENROLL_STATES entering state 10 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.094: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.094: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.095: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.095: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.095: [egismoc] ENROLL_STATES entering state 11 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.095: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.095: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.095: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.095: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.096: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.096: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.096: Read capture callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.096: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.096: Response suffix valid: NO 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.096: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.096: Response suffix valid: yes 162s (process:4329): libfprint-device-DEBUG: 03:38:29.096: Device reported enroll progress, reported 4 of 10 have been completed 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.096: [egismoc] ENROLL_STATES entering state 8 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.096: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.096: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.096: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.097: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.098: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.098: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.098: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.098: [egismoc] ENROLL_STATES entering state 9 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.098: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.098: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.098: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.099: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.099: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.099: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.099: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.099: [egismoc] ENROLL_STATES entering state 10 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.099: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.100: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.100: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.100: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.100: [egismoc] ENROLL_STATES entering state 11 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.100: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.100: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.100: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.101: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.101: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.101: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.101: Read capture callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.101: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.101: Response suffix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.101: Partial capture successful. Please touch the sensor again (5/10) 162s (process:4329): libfprint-device-DEBUG: 03:38:29.101: Device reported enroll progress, reported 5 of 10 have been completed 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.101: [egismoc] ENROLL_STATES entering state 8 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.101: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.101: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.101: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.102: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.103: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.103: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.103: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.103: [egismoc] ENROLL_STATES entering state 9 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.103: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.103: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.103: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.103: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.104: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.104: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.104: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.104: [egismoc] ENROLL_STATES entering state 10 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.104: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.104: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.105: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.105: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.105: [egismoc] ENROLL_STATES entering state 11 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.105: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.105: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.105: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.106: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.109: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.109: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.109: Read capture callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.109: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.109: Response suffix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.109: Partial capture successful. Please touch the sensor again (6/10) 162s (process:4329): libfprint-device-DEBUG: 03:38:29.109: Device reported enroll progress, reported 6 of 10 have been completed 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.109: [egismoc] ENROLL_STATES entering state 8 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.109: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.109: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.109: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.110: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.110: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.110: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.110: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.110: [egismoc] ENROLL_STATES entering state 9 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.110: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.110: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.110: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.111: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.111: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.112: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.112: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.112: [egismoc] ENROLL_STATES entering state 10 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.112: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.112: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.112: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.112: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.112: [egismoc] ENROLL_STATES entering state 11 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.112: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.112: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.112: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.113: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.113: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.113: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.113: Read capture callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.113: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.113: Response suffix valid: NO 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.113: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.113: Response suffix valid: yes 162s (process:4329): libfprint-device-DEBUG: 03:38:29.113: Device reported enroll progress, reported 6 of 10 have been completed 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.113: [egismoc] ENROLL_STATES entering state 8 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.113: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.113: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.113: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.114: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.114: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.115: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.115: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.115: [egismoc] ENROLL_STATES entering state 9 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.115: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.115: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.115: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.115: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.116: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.116: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.116: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.116: [egismoc] ENROLL_STATES entering state 10 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.116: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.116: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.116: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.116: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.116: [egismoc] ENROLL_STATES entering state 11 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.116: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.116: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.116: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.117: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.117: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.117: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.117: Read capture callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.117: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.117: Response suffix valid: NO 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.117: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.117: Response suffix valid: yes 162s (process:4329): libfprint-device-DEBUG: 03:38:29.117: Device reported enroll progress, reported 6 of 10 have been completed 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.118: [egismoc] ENROLL_STATES entering state 8 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.118: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.118: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.118: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.118: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.119: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.119: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.119: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.119: [egismoc] ENROLL_STATES entering state 9 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.119: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.119: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.119: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.119: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.120: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.120: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.120: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.120: [egismoc] ENROLL_STATES entering state 10 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.120: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.120: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.121: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.121: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.121: [egismoc] ENROLL_STATES entering state 11 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.121: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.121: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.121: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.121: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.122: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.122: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.122: Read capture callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.122: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.122: Response suffix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.122: Partial capture successful. Please touch the sensor again (7/10) 162s (process:4329): libfprint-device-DEBUG: 03:38:29.122: Device reported enroll progress, reported 7 of 10 have been completed 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.122: [egismoc] ENROLL_STATES entering state 8 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.122: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.122: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.122: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.122: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.123: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.123: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.123: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.123: [egismoc] ENROLL_STATES entering state 9 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.123: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.123: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.123: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.124: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.124: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.124: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.124: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.124: [egismoc] ENROLL_STATES entering state 10 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.124: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.124: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.125: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.125: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.125: [egismoc] ENROLL_STATES entering state 11 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.125: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.125: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.125: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.126: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.126: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.126: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.126: Read capture callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.126: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.126: Response suffix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.126: Partial capture successful. Please touch the sensor again (8/10) 162s (process:4329): libfprint-device-DEBUG: 03:38:29.126: Device reported enroll progress, reported 8 of 10 have been completed 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.126: [egismoc] ENROLL_STATES entering state 8 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.126: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.126: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.126: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.127: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.127: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.127: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.127: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.127: [egismoc] ENROLL_STATES entering state 9 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.127: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.127: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.127: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.128: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.128: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.129: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.129: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.129: [egismoc] ENROLL_STATES entering state 10 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.129: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.129: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.129: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.129: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.129: [egismoc] ENROLL_STATES entering state 11 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.129: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.129: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.129: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.130: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.130: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.130: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.130: Read capture callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.130: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.130: Response suffix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.130: Partial capture successful. Please touch the sensor again (9/10) 162s (process:4329): libfprint-device-DEBUG: 03:38:29.130: Device reported enroll progress, reported 9 of 10 have been completed 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.130: [egismoc] ENROLL_STATES entering state 8 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.130: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.130: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.130: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.131: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.131: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.131: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.131: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.131: [egismoc] ENROLL_STATES entering state 9 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.131: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.131: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.131: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.132: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.132: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.132: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.132: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.132: [egismoc] ENROLL_STATES entering state 10 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.132: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.132: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.135: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.135: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.135: [egismoc] ENROLL_STATES entering state 11 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.135: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.135: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.135: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.135: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.136: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.136: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.136: Read capture callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.136: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.136: Response suffix valid: NO 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.136: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.136: Response suffix valid: yes 162s (process:4329): libfprint-device-DEBUG: 03:38:29.136: Device reported enroll progress, reported 9 of 10 have been completed 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.136: [egismoc] ENROLL_STATES entering state 8 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.136: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.136: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.136: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.137: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.137: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.137: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.137: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.137: [egismoc] ENROLL_STATES entering state 9 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.137: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.137: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.137: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.138: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.138: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.138: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.138: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.139: [egismoc] ENROLL_STATES entering state 10 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.139: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.139: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.139: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.139: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.139: [egismoc] ENROLL_STATES entering state 11 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.139: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.139: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.139: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.140: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.141: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.141: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.141: Read capture callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.141: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.141: Response suffix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.141: Partial capture successful. Please touch the sensor again (10/10) 162s (process:4329): libfprint-device-DEBUG: 03:38:29.141: Device reported enroll progress, reported 10 of 10 have been completed 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.141: [egismoc] ENROLL_STATES entering state 12 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.141: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.141: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.141: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.141: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.142: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.142: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.142: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.142: [egismoc] ENROLL_STATES entering state 13 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.142: New fingerprint ID: FP1-00000000-2-00000000-nobody 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.142: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.142: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.142: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.142: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.143: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.143: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.143: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.143: [egismoc] ENROLL_STATES entering state 14 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.143: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.143: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.143: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.144: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.145: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.145: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.145: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.145: [egismoc] ENROLL_STATES entering state 15 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.145: Enrollment was successful! 162s (process:4329): libfprint-device-DEBUG: 03:38:29.145: Device reported enroll completion 162s (process:4329): libfprint-device-DEBUG: 03:38:29.145: Device reported finger status change: FP_FINGER_STATUS_NONE 162s (process:4329): libfprint-device-DEBUG: 03:38:29.145: Print for finger FP_FINGER_LEFT_INDEX enrolled 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.145: [egismoc] ENROLL_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.145: Task SSM done 162s (process:4329): libfprint-device-DEBUG: 03:38:29.145: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 162s (process:4329): libfprint-device-DEBUG: 03:38:29.145: Updated temperature model after 0.08 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.145: List 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.145: [egismoc] LIST_STATES entering state 0 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.145: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.145: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.145: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.145: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.146: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.146: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.146: List callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.146: Device fingerprint 1: FP1-00000000-2-00000000-nobody 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.146: Number of currently enrolled fingerprints on the device is 1 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.146: [egismoc] LIST_STATES entering state 1 162s (process:4329): libfprint-device-DEBUG: 03:38:29.146: Device reported listing completion 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.146: [egismoc] LIST_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.146: Task SSM done 162s (process:4329): libfprint-device-DEBUG: 03:38:29.146: Completing action FPI_DEVICE_ACTION_LIST in idle! 162s (process:4329): libfprint-device-DEBUG: 03:38:29.146: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 162s (process:4329): libfprint-device-DEBUG: 03:38:29.146: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.146: Identify or Verify 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.146: [egismoc] IDENTIFY_STATES entering state 0 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.146: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.146: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.146: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.147: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.148: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.148: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.148: List callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.148: Device fingerprint 1: FP1-00000000-2-00000000-nobody 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.148: Number of currently enrolled fingerprints on the device is 1 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.148: [egismoc] IDENTIFY_STATES entering state 1 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.148: [egismoc] IDENTIFY_STATES entering state 2 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.148: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.148: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.148: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.148: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.149: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.149: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.149: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.149: [egismoc] IDENTIFY_STATES entering state 3 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.149: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.149: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.149: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.151: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.151: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.151: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.151: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.152: [egismoc] IDENTIFY_STATES entering state 4 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.152: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.152: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.152: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.152: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.152: [egismoc] IDENTIFY_STATES entering state 5 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.152: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.152: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.152: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.153: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.153: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.153: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.153: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.153: [egismoc] IDENTIFY_STATES entering state 6 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.153: Get check command 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.153: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.153: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.153: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.154: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.154: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.154: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.154: Identify check callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.154: Response suffix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.154: Identify successful for: FP1-00000000-2-00000000-nobody 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.154: Verifying against: FP1-00000000-2-00000000-nobody 162s (process:4329): libfprint-device-DEBUG: 03:38:29.154: Device reported verify result 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.154: [egismoc] IDENTIFY_STATES entering state 7 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.154: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.154: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.154: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.155: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.156: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.156: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.156: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.156: [egismoc] IDENTIFY_STATES entering state 8 162s (process:4329): libfprint-device-DEBUG: 03:38:29.156: Device reported verify completion 162s (process:4329): libfprint-device-DEBUG: 03:38:29.156: Device reported finger status change: FP_FINGER_STATUS_NONE 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.156: [egismoc] IDENTIFY_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.156: Task SSM done 162s (process:4329): libfprint-device-DEBUG: 03:38:29.156: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 162s (process:4329): libfprint-device-DEBUG: 03:38:29.156: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 162s (process:4329): libfprint-device-DEBUG: 03:38:29.156: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.156: Identify or Verify 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.156: [egismoc] IDENTIFY_STATES entering state 0 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.156: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.156: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.156: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.157: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.158: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.158: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.158: List callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.158: Device fingerprint 1: FP1-00000000-2-00000000-nobody 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.158: Number of currently enrolled fingerprints on the device is 1 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.158: [egismoc] IDENTIFY_STATES entering state 1 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.158: [egismoc] IDENTIFY_STATES entering state 2 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.158: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.158: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.158: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.159: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.159: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.159: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.159: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.159: [egismoc] IDENTIFY_STATES entering state 3 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.159: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.159: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.159: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.160: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.160: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.160: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.160: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.160: [egismoc] IDENTIFY_STATES entering state 4 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.160: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.160: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.161: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.161: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.161: [egismoc] IDENTIFY_STATES entering state 5 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.161: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.161: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.161: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.162: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.162: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.162: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.162: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.162: [egismoc] IDENTIFY_STATES entering state 6 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.162: Get check command 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.162: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.162: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.162: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.163: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.164: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.164: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.164: Identify check callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.164: Response suffix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.164: Identify successful for: FP1-00000000-2-00000000-nobody 162s (process:4329): libfprint-device-DEBUG: 03:38:29.164: Device reported identify result 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.164: [egismoc] IDENTIFY_STATES entering state 7 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.164: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.164: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.164: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.165: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.166: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.166: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.166: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.166: [egismoc] IDENTIFY_STATES entering state 8 162s (process:4329): libfprint-device-DEBUG: 03:38:29.166: Device reported identify completion 162s (process:4329): libfprint-device-DEBUG: 03:38:29.166: Device reported finger status change: FP_FINGER_STATUS_NONE 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.166: [egismoc] IDENTIFY_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.166: Task SSM done 162s (process:4329): libfprint-device-DEBUG: 03:38:29.166: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 162s (process:4329): libfprint-device-DEBUG: 03:38:29.166: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 162s (process:4329): libfprint-device-DEBUG: 03:38:29.166: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.166: Enroll 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.166: [egismoc] ENROLL_STATES entering state 0 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.166: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.166: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.166: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.167: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.167: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.168: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.168: List callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.168: Device fingerprint 1: FP1-00000000-2-00000000-nobody 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.168: Number of currently enrolled fingerprints on the device is 1 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.168: [egismoc] ENROLL_STATES entering state 1 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.168: [egismoc] ENROLL_STATES entering state 2 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.168: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.168: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.168: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.169: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.169: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.169: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.169: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.169: [egismoc] ENROLL_STATES entering state 3 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.169: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.169: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.169: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.170: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.170: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.170: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.170: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.170: [egismoc] ENROLL_STATES entering state 4 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.170: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.170: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.171: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.171: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.171: [egismoc] ENROLL_STATES entering state 5 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.171: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.171: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.171: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.172: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.172: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.172: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.172: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.172: [egismoc] ENROLL_STATES entering state 6 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.172: Get check command 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.172: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.172: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.172: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.173: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.174: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.174: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.174: Enroll check callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.174: Response suffix valid: NO 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.174: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.174: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.174: Task SSM done 162s (process:4329): libfprint-device-DEBUG: 03:38:29.174: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL 162s (process:4329): libfprint-device-DEBUG: 03:38:29.174: Device reported enroll completion 162s (process:4329): libfprint-device-DEBUG: 03:38:29.174: Device reported finger status change: FP_FINGER_STATUS_NONE 162s (process:4329): libfprint-device-DEBUG: 03:38:29.174: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 162s (process:4329): libfprint-device-DEBUG: 03:38:29.174: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.174: List 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.174: [egismoc] LIST_STATES entering state 0 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.174: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.174: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.174: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.174: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.175: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.175: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.175: List callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.175: Device fingerprint 1: FP1-00000000-2-00000000-nobody 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.175: Number of currently enrolled fingerprints on the device is 1 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.175: [egismoc] LIST_STATES entering state 1 162s (process:4329): libfprint-device-DEBUG: 03:38:29.175: Device reported listing completion 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.175: [egismoc] LIST_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.175: Task SSM done 162s (process:4329): libfprint-device-DEBUG: 03:38:29.175: Completing action FPI_DEVICE_ACTION_LIST in idle! 162s (process:4329): libfprint-device-DEBUG: 03:38:29.175: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 162s (process:4329): libfprint-device-DEBUG: 03:38:29.175: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.175: Enroll 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.175: [egismoc] ENROLL_STATES entering state 0 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.175: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.175: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.175: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.176: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.177: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.177: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.177: List callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.177: Device fingerprint 1: FP1-00000000-2-00000000-nobody 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.177: Number of currently enrolled fingerprints on the device is 1 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.177: [egismoc] ENROLL_STATES entering state 1 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.177: [egismoc] ENROLL_STATES entering state 2 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.177: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.177: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.177: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.177: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.178: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.178: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.178: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.178: [egismoc] ENROLL_STATES entering state 3 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.178: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.178: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.178: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.178: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.179: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.179: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.179: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.179: [egismoc] ENROLL_STATES entering state 4 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.179: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.179: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.180: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.180: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.180: [egismoc] ENROLL_STATES entering state 5 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.180: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.180: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.180: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.180: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.181: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.181: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.181: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.181: [egismoc] ENROLL_STATES entering state 6 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.181: Get check command 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.181: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.181: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.181: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.181: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.182: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.182: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.182: Enroll check callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.182: Response suffix valid: yes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.182: [egismoc] ENROLL_STATES entering state 7 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.182: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.182: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.182: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.183: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.183: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.183: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.183: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.183: [egismoc] ENROLL_STATES entering state 8 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.183: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.183: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.183: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.184: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.184: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.185: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.185: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.185: [egismoc] ENROLL_STATES entering state 9 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.185: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.185: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.185: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.185: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.186: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.186: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.186: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.186: [egismoc] ENROLL_STATES entering state 10 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.186: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.186: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.186: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.186: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.186: [egismoc] ENROLL_STATES entering state 11 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.186: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.186: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.186: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.187: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.187: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.187: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.187: Read capture callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.187: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.187: Response suffix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.187: Partial capture successful. Please touch the sensor again (1/10) 162s (process:4329): libfprint-device-DEBUG: 03:38:29.187: Device reported enroll progress, reported 1 of 10 have been completed 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.187: [egismoc] ENROLL_STATES entering state 8 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.187: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.187: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.187: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.188: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.189: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.189: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.189: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.189: [egismoc] ENROLL_STATES entering state 9 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.189: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.189: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.189: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.189: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.190: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.190: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.190: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.190: [egismoc] ENROLL_STATES entering state 10 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.190: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.190: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.191: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.191: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.191: [egismoc] ENROLL_STATES entering state 11 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.191: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.191: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.191: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.191: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.192: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.192: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.192: Read capture callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.192: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.192: Response suffix valid: NO 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.192: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.192: Response suffix valid: yes 162s (process:4329): libfprint-device-DEBUG: 03:38:29.192: Device reported enroll progress, reported 1 of 10 have been completed 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.192: [egismoc] ENROLL_STATES entering state 8 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.192: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.192: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.192: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.192: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.193: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.193: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.193: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.193: [egismoc] ENROLL_STATES entering state 9 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.193: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.193: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.193: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.196: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.197: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.197: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.197: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.197: [egismoc] ENROLL_STATES entering state 10 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.197: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.197: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.198: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.198: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.198: [egismoc] ENROLL_STATES entering state 11 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.198: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.198: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.198: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.198: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.199: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.199: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.199: Read capture callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.199: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.199: Response suffix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.199: Partial capture successful. Please touch the sensor again (2/10) 162s (process:4329): libfprint-device-DEBUG: 03:38:29.199: Device reported enroll progress, reported 2 of 10 have been completed 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.199: [egismoc] ENROLL_STATES entering state 8 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.199: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.199: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.199: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.200: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.200: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.200: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.200: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.200: [egismoc] ENROLL_STATES entering state 9 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.200: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.200: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.200: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.201: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.201: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.201: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.201: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.201: [egismoc] ENROLL_STATES entering state 10 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.201: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.201: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.202: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.202: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.202: [egismoc] ENROLL_STATES entering state 11 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.202: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.202: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.202: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.203: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.203: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.203: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.203: Read capture callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.203: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.203: Response suffix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.203: Partial capture successful. Please touch the sensor again (3/10) 162s (process:4329): libfprint-device-DEBUG: 03:38:29.203: Device reported enroll progress, reported 3 of 10 have been completed 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.203: [egismoc] ENROLL_STATES entering state 8 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.203: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.203: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.203: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.204: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.204: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.204: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.204: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.204: [egismoc] ENROLL_STATES entering state 9 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.204: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.204: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.204: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.205: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.206: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.206: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.206: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.206: [egismoc] ENROLL_STATES entering state 10 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.206: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.206: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.206: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.206: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.206: [egismoc] ENROLL_STATES entering state 11 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.206: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.206: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.206: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.207: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.207: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.207: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.207: Read capture callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.207: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.207: Response suffix valid: NO 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.207: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.207: Response suffix valid: yes 162s (process:4329): libfprint-device-DEBUG: 03:38:29.207: Device reported enroll progress, reported 3 of 10 have been completed 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.208: [egismoc] ENROLL_STATES entering state 8 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.208: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.208: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.208: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.208: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.210: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.210: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.210: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.210: [egismoc] ENROLL_STATES entering state 9 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.210: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.210: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.210: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.210: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.213: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.213: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.213: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.213: [egismoc] ENROLL_STATES entering state 10 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.213: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.213: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.214: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.214: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.214: [egismoc] ENROLL_STATES entering state 11 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.214: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.214: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.214: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.214: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.215: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.215: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.215: Read capture callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.215: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.215: Response suffix valid: NO 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.215: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.215: Response suffix valid: yes 162s (process:4329): libfprint-device-DEBUG: 03:38:29.215: Device reported enroll progress, reported 3 of 10 have been completed 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.215: [egismoc] ENROLL_STATES entering state 8 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.215: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.215: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.215: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.216: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.216: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.216: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.217: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.217: [egismoc] ENROLL_STATES entering state 9 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.217: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.217: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.217: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.217: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.218: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.218: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.218: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.218: [egismoc] ENROLL_STATES entering state 10 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.218: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.218: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.218: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.218: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.218: [egismoc] ENROLL_STATES entering state 11 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.218: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.218: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.218: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.219: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.220: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.220: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.220: Read capture callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.220: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.220: Response suffix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.220: Partial capture successful. Please touch the sensor again (4/10) 162s (process:4329): libfprint-device-DEBUG: 03:38:29.220: Device reported enroll progress, reported 4 of 10 have been completed 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.220: [egismoc] ENROLL_STATES entering state 8 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.220: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.220: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.220: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.220: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.225: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.225: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.225: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.225: [egismoc] ENROLL_STATES entering state 9 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.225: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.225: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.225: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.226: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.227: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.227: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.227: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.227: [egismoc] ENROLL_STATES entering state 10 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.227: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.227: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.227: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.227: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.227: [egismoc] ENROLL_STATES entering state 11 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.227: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.227: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.227: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.229: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.229: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.229: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.229: Read capture callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.229: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.229: Response suffix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.229: Partial capture successful. Please touch the sensor again (5/10) 162s (process:4329): libfprint-device-DEBUG: 03:38:29.229: Device reported enroll progress, reported 5 of 10 have been completed 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.230: [egismoc] ENROLL_STATES entering state 8 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.230: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.230: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.230: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.230: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.231: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.231: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.231: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.231: [egismoc] ENROLL_STATES entering state 9 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.231: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.231: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.231: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.231: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.232: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.232: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.232: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.232: [egismoc] ENROLL_STATES entering state 10 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.232: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.232: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.233: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.233: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.234: [egismoc] ENROLL_STATES entering state 11 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.234: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.234: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.234: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.234: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.236: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.237: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.237: Read capture callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.237: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.237: Response suffix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.237: Partial capture successful. Please touch the sensor again (6/10) 162s (process:4329): libfprint-device-DEBUG: 03:38:29.237: Device reported enroll progress, reported 6 of 10 have been completed 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.237: [egismoc] ENROLL_STATES entering state 8 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.237: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.237: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.237: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.237: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.238: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.238: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.238: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.238: [egismoc] ENROLL_STATES entering state 9 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.238: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.238: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.238: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.238: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.239: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.239: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.239: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.239: [egismoc] ENROLL_STATES entering state 10 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.239: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.239: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.240: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.240: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.240: [egismoc] ENROLL_STATES entering state 11 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.240: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.240: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.240: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.240: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.241: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.241: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.241: Read capture callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.241: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.241: Response suffix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.241: Partial capture successful. Please touch the sensor again (7/10) 162s (process:4329): libfprint-device-DEBUG: 03:38:29.241: Device reported enroll progress, reported 7 of 10 have been completed 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.241: [egismoc] ENROLL_STATES entering state 8 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.241: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.241: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.241: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.241: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.242: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.242: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.242: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.242: [egismoc] ENROLL_STATES entering state 9 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.242: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.242: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.242: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.243: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.243: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.243: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.243: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.243: [egismoc] ENROLL_STATES entering state 10 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.243: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.243: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.244: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.244: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.244: [egismoc] ENROLL_STATES entering state 11 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.244: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.244: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.244: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.245: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.246: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.246: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.246: Read capture callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.246: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.246: Response suffix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.246: Partial capture successful. Please touch the sensor again (8/10) 162s (process:4329): libfprint-device-DEBUG: 03:38:29.246: Device reported enroll progress, reported 8 of 10 have been completed 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.246: [egismoc] ENROLL_STATES entering state 8 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.246: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.246: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.246: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.247: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.247: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.247: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.247: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.247: [egismoc] ENROLL_STATES entering state 9 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.247: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.247: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.247: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.248: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.249: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.249: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.249: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.249: [egismoc] ENROLL_STATES entering state 10 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.249: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.249: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.249: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.249: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.249: [egismoc] ENROLL_STATES entering state 11 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.249: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.249: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.249: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.250: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.250: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.250: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.250: Read capture callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.250: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.250: Response suffix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.250: Partial capture successful. Please touch the sensor again (9/10) 162s (process:4329): libfprint-device-DEBUG: 03:38:29.250: Device reported enroll progress, reported 9 of 10 have been completed 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.250: [egismoc] ENROLL_STATES entering state 8 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.250: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.250: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.250: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.251: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.252: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.252: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.252: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.252: [egismoc] ENROLL_STATES entering state 9 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.252: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.252: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.252: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.252: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.253: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.253: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.253: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.253: [egismoc] ENROLL_STATES entering state 10 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.253: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.253: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.253: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.253: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.253: [egismoc] ENROLL_STATES entering state 11 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.253: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.253: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.253: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.254: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.255: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.255: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.255: Read capture callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.255: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.255: Response suffix valid: NO 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.255: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.255: Response suffix valid: yes 162s (process:4329): libfprint-device-DEBUG: 03:38:29.255: Device reported enroll progress, reported 9 of 10 have been completed 162s listing - device should have prints 162s clear device storage 162s clear done 162s listing - device should be empty 162s enrolling 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6513fc38e740 (FpiDeviceEgisMoc at 0x130357b0)>, 1, , None, None) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6513fc38e740 (FpiDeviceEgisMoc at 0x130357b0)>, 2, , None, None) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6513fc38e740 (FpiDeviceEgisMoc at 0x130357b0)>, 2, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6513fc38e740 (FpiDeviceEgisMoc at 0x130357b0)>, 3, , None, None) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6513fc38e740 (FpiDeviceEgisMoc at 0x130357b0)>, 4, , None, None) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6513fc38e740 (FpiDeviceEgisMoc at 0x130357b0)>, 4, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6513fc38e740 (FpiDeviceEgisMoc at 0x130357b0)>, 5, , None, None) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6513fc38e740 (FpiDeviceEgisMoc at 0x130357b0)>, 6, , None, None) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6513fc38e740 (FpiDeviceEgisMoc at 0x130357b0)>, 6, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6513fc38e740 (FpiDeviceEgisMoc at 0x130357b0)>, 6, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6513fc38e740 (FpiDeviceEgisMoc at 0x130357b0)>, 7, , None, None) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6513fc38e740 (FpiDeviceEgisMoc at 0x130357b0)>, 8, , None, None) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6513fc38e740 (FpiDeviceEgisMoc at 0x130357b0)>, 9, , None, None) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6513fc38e740 (FpiDeviceEgisMoc at 0x130357b0)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6513fc38e740 (FpiDeviceEgisMoc at 0x130357b0)>, 10, , None, None) 162s enroll done 162s listing - device should have 1 print 162s verifying 162s verify done 162s async identifying 162s indentification_done: 162s try to enroll duplicate 162s duplicate enroll attempt done 162s listing - device should still only have 1 print 162s enroll new finger 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6513fc38e740 (FpiDeviceEgisMoc at 0x130357b0)>, 1, , None, None) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6513fc38e740 (FpiDeviceEgisMoc at 0x130357b0)>, 1, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6513fc38e740 (FpiDeviceEgisMoc at 0x130357b0)>, 2, , None, None) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6513fc38e740 (FpiDeviceEgisMoc at 0x130357b0)>, 3, , None, None) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6513fc38e740 (FpiDeviceEgisMoc at 0x130357b0)>, 3, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6513fc38e740 (FpiDeviceEgisMoc at 0x130357b0)>, 3, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6513fc38e740 (FpiDeviceEgisMoc at 0x130357b0)>, 4, , None, None) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6513fc38e740 (FpiDeviceEgisMoc at 0x130357b0)>, 5, , None, None) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6513fc38e740 (FpiDeviceEgisMoc at 0x130357b0)>, 6, , None, None) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6513fc38e740 (FpiDeviceEgisMoc at 0x130357b0)>, 7, , None, None) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6513fc38e740 (FpiDeviceEgisMoc at 0x130357b0)>, 8, , None, None) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6513fc38e740 (FpiDeviceEgisMoc at 0x130357b0)>, 9, , None, None) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6513fc38e740 (FpiDeviceEgisMoc at 0x130357b0)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))(process:4329): libfprint-SSM-DEBUG: 03:38:29.255: [egismoc] ENROLL_STATES entering state 8 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.255: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.255: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.255: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.255: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.256: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.256: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.256: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.256: [egismoc] ENROLL_STATES entering state 9 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.256: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.256: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.256: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.257: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.257: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.257: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.257: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.257: [egismoc] ENROLL_STATES entering state 10 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.257: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.257: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.258: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.258: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.258: [egismoc] ENROLL_STATES entering state 11 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.258: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.258: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.258: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.258: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.259: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.259: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.259: Read capture callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.259: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.259: Response suffix valid: NO 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.259: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.259: Response suffix valid: yes 162s (process:4329): libfprint-device-DEBUG: 03:38:29.259: Device reported enroll progress, reported 9 of 10 have been completed 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.259: [egismoc] ENROLL_STATES entering state 8 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.259: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.259: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.259: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.260: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.260: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.260: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.260: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.260: [egismoc] ENROLL_STATES entering state 9 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.260: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.260: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.260: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.261: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.262: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.262: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.262: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.262: [egismoc] ENROLL_STATES entering state 10 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.262: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.262: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.262: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.262: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.262: [egismoc] ENROLL_STATES entering state 11 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.262: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.262: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.262: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.263: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.263: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.263: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.263: Read capture callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.263: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.263: Response suffix valid: NO 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.263: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.263: Response suffix valid: yes 162s (process:4329): libfprint-device-DEBUG: 03:38:29.264: Device reported enroll progress, reported 9 of 10 have been completed 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.264: [egismoc] ENROLL_STATES entering state 8 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.264: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.264: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.264: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.264: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.265: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.265: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.265: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.265: [egismoc] ENROLL_STATES entering state 9 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.265: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.265: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.265: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.265: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.266: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.266: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.266: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.266: [egismoc] ENROLL_STATES entering state 10 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.266: Wait for finger on sensor 162s (process:4329): libfprint-device-DEBUG: 03:38:29.266: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.267: Finger on sensor callback 162s (process:4329): libfprint-device-DEBUG: 03:38:29.267: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.267: [egismoc] ENROLL_STATES entering state 11 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.267: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.267: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.267: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.267: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.268: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.268: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.268: Read capture callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.268: Response prefix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.268: Response suffix valid: yes 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.268: Partial capture successful. Please touch the sensor again (10/10) 162s (process:4329): libfprint-device-DEBUG: 03:38:29.268: Device reported enroll progress, reported 10 of 10 have been completed 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.268: [egismoc] ENROLL_STATES entering state 12 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.268: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.268: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.268: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.268: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.269: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.269: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.269: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.269: [egismoc] ENROLL_STATES entering state 13 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.269: New fingerprint ID: FP1-00000000-7-00000000-nobody 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.269: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.269: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.269: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.270: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.270: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.270: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.270: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.270: [egismoc] ENROLL_STATES entering state 14 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.270: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.270: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.270: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.271: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.271: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.272: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.272: Task SSM next state callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.272: [egismoc] ENROLL_STATES entering state 15 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.272: Enrollment was successful! 162s (process:4329): libfprint-device-DEBUG: 03:38:29.272: Device reported enroll completion 162s (process:4329): libfprint-device-DEBUG: 03:38:29.272: Device reported finger status change: FP_FINGER_STATUS_NONE 162s (process:4329): libfprint-device-DEBUG: 03:38:29.272: Print for finger FP_FINGER_RIGHT_INDEX enrolled 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.272: [egismoc] ENROLL_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.272: Task SSM done 162s (process:4329): libfprint-device-DEBUG: 03:38:29.272: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 162s (process:4329): libfprint-device-DEBUG: 03:38:29.272: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.272: List 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.272: [egismoc] LIST_STATES entering state 0 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.272: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.272: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.272: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.272: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.273: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.273: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.273: List callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.273: Device fingerprint 1: FP1-00000000-2-00000000-nobody 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.273: Device fingerprint 2: FP1-00000000-7-00000000-nobody 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.273: Number of currently enrolled fingerprints on the device is 2 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.273: [egismoc] LIST_STATES entering state 1 162s (process:4329): libfprint-device-DEBUG: 03:38:29.273: Device reported listing completion 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.273: [egismoc] LIST_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.273: Task SSM done 162s (process:4329): libfprint-device-DEBUG: 03:38:29.273: Completing action FPI_DEVICE_ACTION_LIST in idle! 162s (process:4329): libfprint-device-DEBUG: 03:38:29.273: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.273: Delete 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.273: [egismoc] DELETE_STATES entering state 0 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.273: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.273: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.273: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.274: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.274: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.274: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.274: List callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.274: Device fingerprint 1: FP1-00000000-2-00000000-nobody 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.274: Device fingerprint 2: FP1-00000000-7-00000000-nobody 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.274: Number of currently enrolled fingerprints on the device is 2 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.275: [egismoc] DELETE_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.275: Get delete command 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.275: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody) 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.275: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.275: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.275: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.275: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.276: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.276: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.276: Delete callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.276: Response prefix valid: yes 162s (process:4329): libfprint-device-DEBUG: 03:38:29.276: Device reported deletion completion 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.276: [egismoc] DELETE_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.276: Task SSM done 162s (process:4329): libfprint-device-DEBUG: 03:38:29.276: Completing action FPI_DEVICE_ACTION_DELETE in idle! 162s (process:4329): libfprint-device-DEBUG: 03:38:29.276: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.276: List 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.276: [egismoc] LIST_STATES entering state 0 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.276: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.276: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.276: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.277: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.278: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.278: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.278: List callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.278: Device fingerprint 1: FP1-00000000-7-00000000-nobody 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.278: Number of currently enrolled fingerprints on the device is 1 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.278: [egismoc] LIST_STATES entering state 1 162s (process:4329): libfprint-device-DEBUG: 03:38:29.278: Device reported listing completion 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.278: [egismoc] LIST_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.278: Task SSM done 162s (process:4329): libfprint-device-DEBUG: 03:38:29.278: Completing action FPI_DEVICE_ACTION_LIST in idle! 162s (process:4329): libfprint-device-DEBUG: 03:38:29.278: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.278: Clear storage 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.278: [egismoc] DELETE_STATES entering state 0 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.278: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.278: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.278: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.279: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.279: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.279: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.280: List callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.280: Device fingerprint 1: FP1-00000000-7-00000000-nobody 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.280: Number of currently enrolled fingerprints on the device is 1 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.280: [egismoc] DELETE_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.280: Get delete command 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.280: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.280: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.280: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.280: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.281: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.281: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.281: Delete callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.281: Response prefix valid: yes 162s (process:4329): libfprint-device-DEBUG: 03:38:29.281: Device reported deletion completion 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.281: [egismoc] DELETE_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.281: Task SSM done 162s (process:4329): libfprint-device-DEBUG: 03:38:29.281: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 162s (process:4329): libfprint-device-DEBUG: 03:38:29.281: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.281: List 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.281: [egismoc] LIST_STATES entering state 0 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.281: Execute command and get response 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.281: Get check bytes 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.281: [egismoc] CMD_STATES entering state 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.282: [egismoc] CMD_STATES entering state 1 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.282: Command receive callback 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.282: [egismoc] CMD_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.283: List callback 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.283: Number of currently enrolled fingerprints on the device is 0 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.283: [egismoc] LIST_STATES entering state 1 162s (process:4329): libfprint-device-DEBUG: 03:38:29.283: Device reported listing completion 162s (process:4329): libfprint-SSM-DEBUG: 03:38:29.283: [egismoc] LIST_STATES completed successfully 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.283: Task SSM done 162s (process:4329): libfprint-device-DEBUG: 03:38:29.283: Completing action FPI_DEVICE_ACTION_LIST in idle! 162s (process:4329): libfprint-device-DEBUG: 03:38:29.283: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.283: Closing device 162s (process:4329): libfprint-egismoc-DEBUG: 03:38:29.283: Cancel 162s (process:4329): libfprint-device-DEBUG: 03:38:29.283: Device reported close completion 162s (process:4329): libfprint-device-DEBUG: 03:38:29.283: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 162s (process:4329): libfprint-device-DEBUG: 03:38:29.284: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 162s 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6513fc38e740 (FpiDeviceEgisMoc at 0x130357b0)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6513fc38e740 (FpiDeviceEgisMoc at 0x130357b0)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 162s finger status: 162s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x6513fc38e740 (FpiDeviceEgisMoc at 0x130357b0)>, 10, , None, None) 162s enroll new finger done 162s listing - device should have 2 prints 162s deleting first print 162s delete done 162s listing - device should only have second print 162s clear device storage 162s clear done 162s listing - device should be empty 162s ** (umockdev-run:4325): DEBUG: 03:38:29.296: umockdev.vala:154: Removing test bed /tmp/umockdev.L41K22 162s (umockdev-run:4325): GLib-DEBUG: 03:38:29.303: unsetenv() is not thread-safe and should not be used after threads are created 162s PASS: libfprint-2/driver-egismoc.test 162s Running test: libfprint-2/driver-elan.test 162s ** (umockdev-run:4337): DEBUG: 03:38:29.347: umockdev.vala:127: Created udev test bed /tmp/umockdev.3AE512 162s ** (umockdev-run:4337): DEBUG: 03:38:29.348: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4 162s ** (umockdev-run:4337): DEBUG: 03:38:29.349: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4 (subsystem usb) 162s ** (umockdev-run:4337): DEBUG: 03:38:29.352: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3AE512/dev/bus/usb/001/094 162s ** (umockdev-run:4337): DEBUG: 03:38:29.352: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-4 162s ** (umockdev-run:4337): DEBUG: 03:38:29.353: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-4 (subsystem usb) 162s ** (umockdev-run:4337): DEBUG: 03:38:29.356: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3AE512/dev/bus/usb/001/083 162s ** (umockdev-run:4337): DEBUG: 03:38:29.356: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 162s ** (umockdev-run:4337): DEBUG: 03:38:29.357: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 162s ** (umockdev-run:4337): DEBUG: 03:38:29.359: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3AE512/dev/bus/usb/001/001 162s ** (umockdev-run:4337): DEBUG: 03:38:29.359: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 162s ** (umockdev-run:4337): DEBUG: 03:38:29.360: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 162s (umockdev-run:4337): GLib-GIO-DEBUG: 03:38:29.362: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 162s (process:4341): libfprint-context-DEBUG: 03:38:29.456: Initializing FpContext (libfprint version 1.94.8+tod1) 162s (process:4341): libfprint-tod-DEBUG: 03:38:29.457: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 162s (process:4341): libfprint-context-DEBUG: 03:38:29.459: No driver found for USB device 17EF:1018 162s (process:4341): libfprint-context-DEBUG: 03:38:29.459: No driver found for USB device 1D6B:0002 162s (process:4341): libfprint-device-DEBUG: 03:38:29.459: Device reported probe completion 162s (process:4341): libfprint-device-DEBUG: 03:38:29.459: Completing action FPI_DEVICE_ACTION_PROBE in idle! 162s (process:4341): libfprint-device-DEBUG: 03:38:29.460: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.461: 109268818: ../libfprint/drivers/elan.c:908 162s (process:4341): libfprint-image_device-DEBUG: 03:38:29.461: Image device open completed 162s (process:4341): libfprint-device-DEBUG: 03:38:29.461: Device reported open completion 162s (process:4341): libfprint-device-DEBUG: 03:38:29.461: Completing action FPI_DEVICE_ACTION_OPEN in idle! 162s (process:4341): libfprint-device-DEBUG: 03:38:29.461: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 162s (process:4341): libfprint-device-DEBUG: 03:38:29.461: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 162s (process:4341): libfprint-image_device-DEBUG: 03:38:29.462: Activating image device 162s (process:4341): libfprint-image_device-DEBUG: 03:38:29.462: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.462: 109269704: ../libfprint/drivers/elan.c:960 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.462: 109269721: ../libfprint/drivers/elan.c:951 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.462: 109269736: ../libfprint/drivers/elan.c:892 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.462: 109269751: ../libfprint/drivers/elan.c:100 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.462: [elan] ACTIVATE_NUM_STATES entering state 0 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.462: 109269787: ../libfprint/drivers/elan.c:820 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.462: 109270314: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.462: 109270362: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.462: 109270379: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.463: 109270878: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.463: 109270924: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.463: [elan] ACTIVATE_NUM_STATES entering state 1 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.463: 109271078: ../libfprint/drivers/elan.c:820 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.463: FW ver 0x0140 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.463: [elan] ACTIVATE_NUM_STATES entering state 2 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.463: 109271209: ../libfprint/drivers/elan.c:820 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.464: 109272183: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.464: 109272276: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.464: 109272369: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.465: 109272916: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.465: 109272995: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.465: [elan] ACTIVATE_NUM_STATES entering state 3 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.465: 109273145: ../libfprint/drivers/elan.c:820 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.465: sensor dimensions, WxH: 144x64 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.465: [elan] ACTIVATE_NUM_STATES entering state 4 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.465: 109273161: ../libfprint/drivers/elan.c:820 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.465: skipping command 0x40 0x2a for this device (for devices 0x1 but device is 0x0) 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.465: 109273171: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.465: [elan] ACTIVATE_NUM_STATES completed successfully 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.465: 109273181: ../libfprint/drivers/elan.c:881 162s (process:4341): libfprint-image_device-DEBUG: 03:38:29.465: Image device activation completed 162s (process:4341): libfprint-image_device-DEBUG: 03:38:29.465: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.465: 109273201: ../libfprint/drivers/elan.c:960 162s (process:4341): libfprint-image_device-DEBUG: 03:38:29.465: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.465: 109273214: ../libfprint/drivers/elan.c:960 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.465: 109273219: ../libfprint/drivers/elan.c:792 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.465: 109273223: ../libfprint/drivers/elan.c:100 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.465: [elan] CALIBRATE_NUM_STATES entering state 0 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.465: 109273233: ../libfprint/drivers/elan.c:691 162s (process:4341): libfprint-device-DEBUG: 03:38:29.466: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.466: 109273924: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.466: 109274009: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.466: 109274145: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.467: 109274636: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.467: 109274715: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.467: [elan] CALIBRATE_NUM_STATES entering state 1 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.467: 109274834: ../libfprint/drivers/elan.c:691 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.467: 109274839: ../libfprint/drivers/elan.c:156 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.467: 109274843: ../libfprint/drivers/elan.c:118 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.467: [elan] CALIBRATE_NUM_STATES entering state 2 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.467: 109274859: ../libfprint/drivers/elan.c:691 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.467: 109275503: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.467: 109275579: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.468: 109275672: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.468: 109276173: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.468: 109276267: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.468: [elan] CALIBRATE_NUM_STATES entering state 3 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.468: 109276383: ../libfprint/drivers/elan.c:691 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.468: 109276388: ../libfprint/drivers/elan.c:634 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.468: calibration mean: 8421, bg mean: 5805, delta: 2616 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.468: [elan] CALIBRATE_NUM_STATES entering state 4 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.468: 109276405: ../libfprint/drivers/elan.c:691 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.469: 109276968: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.469: 109277043: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.469: 109277183: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.470: 109277811: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.470: 109277887: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.470: [elan] CALIBRATE_NUM_STATES entering state 5 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.470: 109278043: ../libfprint/drivers/elan.c:691 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.470: calibration status: 0x01 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.520: [elan] CALIBRATE_NUM_STATES entering state 6 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.520: 109328062: ../libfprint/drivers/elan.c:691 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.520: [elan] CALIBRATE_NUM_STATES entering state 4 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.520: 109328089: ../libfprint/drivers/elan.c:691 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.520: 109328551: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.521: 109328605: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.521: 109328641: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.521: 109329208: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.521: 109329218: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.521: [elan] CALIBRATE_NUM_STATES entering state 5 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.521: 109329228: ../libfprint/drivers/elan.c:691 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.521: calibration status: 0x01 162s (process:4341): libfprint-device-DEBUG: 03:38:29.561: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.571: [elan] CALIBRATE_NUM_STATES entering state 6 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.571: 109379308: ../libfprint/drivers/elan.c:691 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.571: [elan] CALIBRATE_NUM_STATES entering state 4 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.571: 109379320: ../libfprint/drivers/elan.c:691 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.572: 109380244: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.572: 109380272: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.572: 109380319: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.573: 109380859: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.573: 109380904: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.573: [elan] CALIBRATE_NUM_STATES entering state 5 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.573: 109381026: ../libfprint/drivers/elan.c:691 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.573: calibration status: 0x01 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.623: [elan] CALIBRATE_NUM_STATES entering state 6 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.623: 109431032: ../libfprint/drivers/elan.c:691 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.623: [elan] CALIBRATE_NUM_STATES entering state 4 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.623: 109431049: ../libfprint/drivers/elan.c:691 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.629: 109437271: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.629: 109437315: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.629: 109437321: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.630: 109437986: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.630: 109438035: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.630: [elan] CALIBRATE_NUM_STATES entering state 5 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.630: 109438052: ../libfprint/drivers/elan.c:691 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.630: calibration status: 0x01 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.681: [elan] CALIBRATE_NUM_STATES entering state 6 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.681: 109488712: ../libfprint/drivers/elan.c:691 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.681: [elan] CALIBRATE_NUM_STATES entering state 4 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.681: 109488726: ../libfprint/drivers/elan.c:691 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.681: 109489467: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.681: 109489521: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.682: 109489657: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.682: 109490233: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.682: 109490285: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.682: [elan] CALIBRATE_NUM_STATES entering state 5 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.682: 109490315: ../libfprint/drivers/elan.c:691 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.682: calibration status: 0x01 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.733: [elan] CALIBRATE_NUM_STATES entering state 6 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.733: 109540712: ../libfprint/drivers/elan.c:691 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.733: [elan] CALIBRATE_NUM_STATES entering state 4 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.733: 109540725: ../libfprint/drivers/elan.c:691 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.737: 109545428: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.737: 109545445: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.737: 109545451: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.738: 109546180: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.738: 109546189: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.738: [elan] CALIBRATE_NUM_STATES entering state 5 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.738: 109546205: ../libfprint/drivers/elan.c:691 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.738: calibration status: 0x03 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.738: [elan] CALIBRATE_NUM_STATES entering state 0 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.738: 109546224: ../libfprint/drivers/elan.c:691 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.739: 109546863: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.739: 109546871: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.739: 109546881: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.739: 109547596: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.739: 109547611: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.739: [elan] CALIBRATE_NUM_STATES entering state 1 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.740: 109547622: ../libfprint/drivers/elan.c:691 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.740: 109547626: ../libfprint/drivers/elan.c:156 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.740: 109547631: ../libfprint/drivers/elan.c:118 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.740: [elan] CALIBRATE_NUM_STATES entering state 2 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.740: 109547650: ../libfprint/drivers/elan.c:691 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.740: 109548293: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.740: 109548310: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.740: 109548315: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.741: 109549048: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.741: 109549056: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.741: [elan] CALIBRATE_NUM_STATES entering state 3 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.741: 109549071: ../libfprint/drivers/elan.c:691 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.741: 109549076: ../libfprint/drivers/elan.c:634 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.741: calibration mean: 8339, bg mean: 8146, delta: 193 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.741: [elan] CALIBRATE_NUM_STATES completed successfully 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.741: 109549102: ../libfprint/drivers/elan.c:776 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.741: 109549106: ../libfprint/drivers/elan.c:620 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.741: 109549111: ../libfprint/drivers/elan.c:100 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.741: [elan] CAPTURE_NUM_STATES entering state 0 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.742: 109549766: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.742: 109549774: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.742: 109549783: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.742: skipping read, not expecting anything 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.742: 109549793: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.742: [elan] CAPTURE_NUM_STATES entering state 1 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.742: 109550428: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.742: 109550436: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.742: 109550446: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.743: 109551136: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.743: 109551144: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.743: [elan] CAPTURE_NUM_STATES entering state 2 162s (process:4341): libfprint-device-DEBUG: 03:38:29.743: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 162s (process:4341): libfprint-image_device-DEBUG: 03:38:29.743: Image device reported finger status: on 162s (process:4341): libfprint-image_device-DEBUG: 03:38:29.743: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.743: 109551191: ../libfprint/drivers/elan.c:960 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.744: 109551860: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.744: 109551868: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.744: 109551878: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.745: 109552691: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.745: 109552710: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.745: [elan] CAPTURE_NUM_STATES entering state 3 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.745: 109552721: ../libfprint/drivers/elan.c:203 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.745: 109552751: ../libfprint/drivers/elan.c:118 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.745: [elan] CAPTURE_NUM_STATES entering state 1 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.745: 109553441: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.745: 109553449: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.745: 109553459: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.746: 109554161: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.746: 109554169: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.746: [elan] CAPTURE_NUM_STATES entering state 2 162s (process:4341): libfprint-image_device-DEBUG: 03:38:29.746: Image device reported finger status: on 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.747: 109554981: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.747: 109554989: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.747: 109554999: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.748: 109555711: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.748: 109555725: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.748: [elan] CAPTURE_NUM_STATES entering state 3 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.748: 109555736: ../libfprint/drivers/elan.c:203 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.748: 109555741: ../libfprint/drivers/elan.c:118 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.748: [elan] CAPTURE_NUM_STATES entering state 1 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.748: 109556400: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.748: 109556416: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.748: 109556421: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.749: 109557140: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.749: 109557148: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.749: [elan] CAPTURE_NUM_STATES entering state 2 162s (process:4341): libfprint-image_device-DEBUG: 03:38:29.749: Image device reported finger status: on 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.750: 109557790: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.750: 109557798: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.750: 109557808: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.750: 109558504: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.750: 109558518: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.750: [elan] CAPTURE_NUM_STATES entering state 3 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.750: 109558529: ../libfprint/drivers/elan.c:203 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.750: 109558533: ../libfprint/drivers/elan.c:118 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.750: [elan] CAPTURE_NUM_STATES entering state 1 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.751: 109559165: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.751: 109559173: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.751: 109559182: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.752: 109559853: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.752: 109559862: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.752: [elan] CAPTURE_NUM_STATES entering state 2 162s (process:4341): libfprint-image_device-DEBUG: 03:38:29.752: Image device reported finger status: on 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.752: 109560518: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.752: 109560534: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.752: 109560540: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.753: 109561246: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.753: 109561260: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.753: [elan] CAPTURE_NUM_STATES entering state 3 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.753: 109561271: ../libfprint/drivers/elan.c:203 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.753: 109561276: ../libfprint/drivers/elan.c:118 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.753: [elan] CAPTURE_NUM_STATES entering state 1 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.754: 109561911: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.754: 109561919: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.754: 109561929: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.754: 109562604: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.754: 109562612: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.755: [elan] CAPTURE_NUM_STATES entering state 2 162s (process:4341): libfprint-image_device-DEBUG: 03:38:29.755: Image device reported finger status: on 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.755: 109563248: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.755: 109563256: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.755: 109563265: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.756: 109563962: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.756: 109563976: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.756: [elan] CAPTURE_NUM_STATES entering state 3 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.756: 109563986: ../libfprint/drivers/elan.c:203 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.756: 109563999: ../libfprint/drivers/elan.c:118 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.756: [elan] CAPTURE_NUM_STATES entering state 1 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.757: 109564697: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.757: 109564705: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.757: 109564715: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.757: 109565362: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.757: 109565370: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.757: [elan] CAPTURE_NUM_STATES entering state 2 162s (process:4341): libfprint-image_device-DEBUG: 03:38:29.757: Image device reported finger status: on 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.758: 109565993: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.758: 109566001: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.758: 109566016: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.759: 109566711: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.759: 109566725: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.759: [elan] CAPTURE_NUM_STATES entering state 3 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.759: 109566736: ../libfprint/drivers/elan.c:203 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.759: 109566740: ../libfprint/drivers/elan.c:118 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.759: [elan] CAPTURE_NUM_STATES entering state 1 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.759: 109567384: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.759: 109567392: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.759: 109567401: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.760: 109568053: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.760: 109568066: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.760: [elan] CAPTURE_NUM_STATES entering state 2 162s (process:4341): libfprint-image_device-DEBUG: 03:38:29.760: Image device reported finger status: on 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.761: 109568707: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.761: 109568728: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.761: 109568735: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.761: 109569370: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.761: 109569381: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.761: [elan] CAPTURE_NUM_STATES entering state 3 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.761: 109569391: ../libfprint/drivers/elan.c:203 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.761: 109569396: ../libfprint/drivers/elan.c:118 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.761: [elan] CAPTURE_NUM_STATES entering state 1 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.762: 109569987: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.762: 109570039: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.762: 109570058: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.763: 109570651: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.763: 109570661: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.763: [elan] CAPTURE_NUM_STATES entering state 2 162s (process:4341): libfprint-image_device-DEBUG: 03:38:29.763: Image device reported finger status: on 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.763: 109571255: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.763: 109571275: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.763: 109571319: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.764: 109571900: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.764: 109571922: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.764: [elan] CAPTURE_NUM_STATES entering state 3 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.764: 109571976: ../libfprint/drivers/elan.c:203 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.764: 109571981: ../libfprint/drivers/elan.c:118 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.764: [elan] CAPTURE_NUM_STATES entering state 1 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.765: 109572653: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.765: 109572715: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.765: 109572732: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.765: 109573332: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.765: 109573351: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.765: [elan] CAPTURE_NUM_STATES entering state 2 162s (process:4341): libfprint-image_device-DEBUG: 03:38:29.765: Image device reported finger status: on 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.766: 109573919: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.766: 109573938: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.766: 109573982: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.767: 109574651: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.767: 109574673: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.767: [elan] CAPTURE_NUM_STATES entering state 3 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.767: 109574685: ../libfprint/drivers/elan.c:203 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.767: 109574690: ../libfprint/drivers/elan.c:118 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.767: [elan] CAPTURE_NUM_STATES entering state 1 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.767: 109575242: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.767: 109575292: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.767: 109575300: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.768: 109575918: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.768: 109575938: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.768: [elan] CAPTURE_NUM_STATES entering state 2 162s (process:4341): libfprint-image_device-DEBUG: 03:38:29.768: Image device reported finger status: on 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.768: 109576530: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.768: 109576557: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.768: 109576564: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.769: 109577230: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.769: 109577242: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.769: [elan] CAPTURE_NUM_STATES entering state 3 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.769: 109577252: ../libfprint/drivers/elan.c:203 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.769: 109577268: ../libfprint/drivers/elan.c:118 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.769: [elan] CAPTURE_NUM_STATES entering state 1 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.770: 109577826: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.770: 109577875: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.770: 109577894: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.770: 109578535: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.770: 109578555: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.770: [elan] CAPTURE_NUM_STATES entering state 2 162s (process:4341): libfprint-image_device-DEBUG: 03:38:29.770: Image device reported finger status: on 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.771: 109579137: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.771: 109579156: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.771: 109579200: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.772: 109579823: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.772: 109579845: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.772: [elan] CAPTURE_NUM_STATES entering state 3 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.772: 109579857: ../libfprint/drivers/elan.c:203 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.772: 109579862: ../libfprint/drivers/elan.c:118 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.772: [elan] CAPTURE_NUM_STATES entering state 1 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.773: 109581090: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.773: 109581142: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.773: 109581149: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.774: 109581720: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.774: 109581768: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.774: [elan] CAPTURE_NUM_STATES entering state 2 162s (process:4341): libfprint-image_device-DEBUG: 03:38:29.774: Image device reported finger status: on 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.774: 109582353: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.774: 109582362: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.774: 109582367: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.775: 109583031: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.775: 109583053: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.775: [elan] CAPTURE_NUM_STATES entering state 3 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.775: 109583106: ../libfprint/drivers/elan.c:203 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.775: 109583111: ../libfprint/drivers/elan.c:118 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.775: [elan] CAPTURE_NUM_STATES entering state 1 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.776: 109583632: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.776: 109583680: ../libfprint/drivers/elan.c:366 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.776: 109583689: ../libfprint/drivers/elan.c:379 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.776: 109584258: ../libfprint/drivers/elan.c:346 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.776: 109584284: ../libfprint/drivers/elan.c:335 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.776: [elan] CAPTURE_NUM_STATES entering state 2 162s (process:4341): libfprint-SSM-DEBUG: 03:38:29.776: [elan] CAPTURE_NUM_STATES completed successfully 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.776: 109584349: ../libfprint/drivers/elan.c:586 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.776: 109584354: ../libfprint/drivers/elan.c:315 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.776: 109584361: ../libfprint/drivers/elan.c:272 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.777: 109585385: ../libfprint/drivers/elan.c:272 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.778: 109586379: ../libfprint/drivers/elan.c:272 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.779: 109587389: ../libfprint/drivers/elan.c:272 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.780: 109588435: ../libfprint/drivers/elan.c:272 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.781: 109589508: ../libfprint/drivers/elan.c:272 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.782: 109590553: ../libfprint/drivers/elan.c:272 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.783: 109591592: ../libfprint/drivers/elan.c:272 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.785: 109592623: ../libfprint/drivers/elan.c:272 162s (process:4341): libfprint-elan-DEBUG: 03:38:29.786: 109593684: ../libfprint/drivers/elan.c:272 162s (process:4341): libfprint-assembling-DEBUG: 03:38:29.908: calc delta completed in 0.121640 secs 163s (process:4341): libfprint-assembling-DEBUG: 03:38:30.028: calc delta completed in 0.119270 secs 163s (process:4341): libfprint-assembling-DEBUG: 03:38:30.028: errors: 233151 rev: 207411 163s (process:4341): libfprint-assembling-DEBUG: 03:38:30.028: height is -185 163s (process:4341): libfprint-image_device-DEBUG: 03:38:30.028: Image device captured an image 163s (process:4341): libfprint-image_device-DEBUG: 03:38:30.028: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 163s (process:4341): libfprint-elan-DEBUG: 03:38:30.029: 109836680: ../libfprint/drivers/elan.c:960 163s (process:4341): libfprint-device-DEBUG: 03:38:30.032: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:4341): libfprint-elan-DEBUG: 03:38:30.032: 109840036: ../libfprint/drivers/elan.c:507 163s (process:4341): libfprint-elan-DEBUG: 03:38:30.032: 109840042: ../libfprint/drivers/elan.c:100 163s (process:4341): libfprint-SSM-DEBUG: 03:38:30.032: [elan] STOP_CAPTURE_NUM_STATES entering state 0 163s (process:4341): libfprint-elan-DEBUG: 03:38:30.032: 109840056: ../libfprint/drivers/elan.c:466 163s (process:4341): libfprint-elan-DEBUG: 03:38:30.033: 109840685: ../libfprint/drivers/elan.c:346 163s (process:4341): libfprint-elan-DEBUG: 03:38:30.033: 109840695: ../libfprint/drivers/elan.c:366 163s (process:4341): libfprint-elan-DEBUG: 03:38:30.033: 109840699: ../libfprint/drivers/elan.c:379 163s (process:4341): libfprint-elan-DEBUG: 03:38:30.033: skipping read, not expecting anything 163s (process:4341): libfprint-elan-DEBUG: 03:38:30.033: 109840717: ../libfprint/drivers/elan.c:335 163s (process:4341): libfprint-SSM-DEBUG: 03:38:30.033: [elan] STOP_CAPTURE_NUM_STATES completed successfully 163s (process:4341): libfprint-elan-DEBUG: 03:38:30.033: 109840728: ../libfprint/drivers/elan.c:483 163s (process:4341): libfprint-device-DEBUG: 03:38:30.033: Device reported finger status change: FP_FINGER_STATUS_NONE 163s (process:4341): libfprint-image_device-DEBUG: 03:38:30.033: Image device reported finger status: off 163s (process:4341): libfprint-image_device-DEBUG: 03:38:30.033: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 163s (process:4341): libfprint-elan-DEBUG: 03:38:30.033: 109840752: ../libfprint/drivers/elan.c:960 163s (process:4341): libfprint-image_device-DEBUG: 03:38:30.033: Deactivating image device 163s (process:4341): libfprint-image_device-DEBUG: 03:38:30.033: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 163s (process:4341): libfprint-elan-DEBUG: 03:38:30.033: 109840768: ../libfprint/drivers/elan.c:960 163s (process:4341): libfprint-elan-DEBUG: 03:38:30.033: 109840773: ../libfprint/drivers/elan.c:975 163s (process:4341): libfprint-image_device-DEBUG: 03:38:30.033: Image device deactivation completed 163s (process:4341): libfprint-image_device-DEBUG: 03:38:30.033: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 163s (process:4341): libfprint-elan-DEBUG: 03:38:30.033: 109840791: ../libfprint/drivers/elan.c:960 163s (process:4341): libfprint-image-DEBUG: 03:38:30.045: Minutiae scan completed in 0.016314 secs 163s (process:4341): libfprint-device-DEBUG: 03:38:30.045: Device reported capture completion 163s (process:4341): libfprint-device-DEBUG: 03:38:30.045: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 163s (process:4341): libfprint-device-DEBUG: 03:38:30.045: Updated temperature model after 0.48 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 163s (process:4341): libfprint-elan-DEBUG: 03:38:30.045: 109853395: ../libfprint/drivers/elan.c:939 163s (process:4341): libfprint-elan-DEBUG: 03:38:30.045: 109853403: ../libfprint/drivers/elan.c:100 163s (process:4341): libfprint-image_device-DEBUG: 03:38:30.046: Image device close completed 163s (process:4341): libfprint-device-DEBUG: 03:38:30.046: Device reported close completion 163s (process:4341): libfprint-device-DEBUG: 03:38:30.046: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 163s (process:4341): libfprint-device-DEBUG: 03:38:30.046: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 163s ** (umockdev-run:4337): DEBUG: 03:38:30.150: umockdev.vala:154: Removing test bed /tmp/umockdev.3AE512 163s (umockdev-run:4337): GLib-DEBUG: 03:38:30.157: unsetenv() is not thread-safe and should not be used after threads are created 163s Comparing PNGs /tmp/libfprint-umockdev-test-tsqhygnr/capture.png and /usr/share/installed-tests/libfprint-2/elan/capture.png 163s PASS: libfprint-2/driver-elan.test 163s Running test: libfprint-2/driver-realtek-5816.test 163s ** (umockdev-run:4350): DEBUG: 03:38:30.217: umockdev.vala:127: Created udev test bed /tmp/umockdev.DML212 163s ** (umockdev-run:4350): DEBUG: 03:38:30.217: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-6 163s ** (umockdev-run:4350): DEBUG: 03:38:30.219: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-6 (subsystem usb) 163s ** (umockdev-run:4350): DEBUG: 03:38:30.223: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.DML212/dev/bus/usb/001/006 163s ** (umockdev-run:4350): DEBUG: 03:38:30.223: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 163s ** (umockdev-run:4350): DEBUG: 03:38:30.224: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 163s ** (umockdev-run:4350): DEBUG: 03:38:30.228: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.DML212/dev/bus/usb/001/001 163s ** (umockdev-run:4350): DEBUG: 03:38:30.228: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 163s ** (umockdev-run:4350): DEBUG: 03:38:30.228: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 163s (process:4354): libfprint-context-DEBUG: 03:38:30.315: Initializing FpContext (libfprint version 1.94.8+tod1) 163s (process:4354): libfprint-tod-DEBUG: 03:38:30.316: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 163s (process:4354): libfprint-context-DEBUG: 03:38:30.318: No driver found for USB device 1D6B:0002 163s (process:4354): libfprint-realtek-DEBUG: 03:38:30.318: 110125982: ../libfprint/drivers/realtek/realtek.c:1225 163s (process:4354): libfprint-realtek-DEBUG: 03:38:30.320: Device name: Realtek USB2.0 Finger Print Bridge 163s (process:4354): libfprint-device-DEBUG: 03:38:30.321: Device reported probe completion 163s (process:4354): libfprint-device-DEBUG: 03:38:30.321: Completing action FPI_DEVICE_ACTION_PROBE in idle! 163s (process:4354): libfprint-device-DEBUG: 03:38:30.321: Not updating temperature model, device can run continuously! 163s (process:4354): libfprint-realtek-DEBUG: 03:38:30.322: 110130088: ../libfprint/drivers/realtek/realtek.c:1270 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.323: [realtek] Init entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.323: [realtek] Init entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.323: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.324: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.324: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.325: [realtek] Init entering state 2 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.325: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.325: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.325: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.326: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.327: [realtek] Init completed successfully 163s (process:4354): libfprint-realtek-DEBUG: 03:38:30.327: Init complete! 163s (process:4354): libfprint-device-DEBUG: 03:38:30.327: Device reported open completion 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.327: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-device-DEBUG: 03:38:30.327: Completing action FPI_DEVICE_ACTION_OPEN in idle! 163s (process:4354): libfprint-device-DEBUG: 03:38:30.327: Not updating temperature model, device can run continuously! 163s (process:4354): libfprint-realtek-DEBUG: 03:38:30.327: 110134709: ../libfprint/drivers/realtek/realtek.c:1333 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.327: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.327: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.327: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-realtek-DEBUG: 03:38:30.328: Successfully cleared storage 163s (process:4354): libfprint-device-DEBUG: 03:38:30.328: Device reported deletion completion 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.328: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-device-DEBUG: 03:38:30.328: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 163s (process:4354): libfprint-device-DEBUG: 03:38:30.328: Not updating temperature model, device can run continuously! 163s (process:4354): libfprint-device-DEBUG: 03:38:30.329: Not updating temperature model, device can run continuously! 163s (process:4354): libfprint-realtek-DEBUG: 03:38:30.329: 110136667: ../libfprint/drivers/realtek/realtek.c:1202 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.329: [realtek] Enroll entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.329: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.329: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.330: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.330: [realtek] Enroll entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.330: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.331: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.331: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.331: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.331: [realtek] Enroll entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.331: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.331: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.332: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.332: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.332: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.333: [realtek] Enroll entering state 3 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.333: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.333: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.333: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.334: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.334: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.334: [realtek] Enroll entering state 4 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.334: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.335: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.335: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.335: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.336: Device reported finger status change: FP_FINGER_STATUS_NONE 163s (process:4354): libfprint-device-DEBUG: 03:38:30.336: Device reported enroll progress, reported 1 of 8 have been completed 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.336: [realtek] Enroll entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.336: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.336: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.336: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.337: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.337: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.337: [realtek] Enroll entering state 3 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.337: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.337: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.338: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.338: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.339: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.339: [realtek] Enroll entering state 4 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.339: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.339: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.339: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.340: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.341: Device reported finger status change: FP_FINGER_STATUS_NONE 163s (process:4354): libfprint-device-DEBUG: 03:38:30.341: Device reported enroll progress, reported 2 of 8 have been completed 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.341: [realtek] Enroll entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.341: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.341: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.341: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.341: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.341: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.342: [realtek] Enroll entering state 3 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.342: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.342: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.343: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.343: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.344: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.344: [realtek] Enroll entering state 4 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.344: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.344: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.344: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.345: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.345: Device reported finger status change: FP_FINGER_STATUS_NONE 163s (process:4354): libfprint-device-DEBUG: 03:38:30.345: Device reported enroll progress, reported 3 of 8 have been completed 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.345: [realtek] Enroll entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.345: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.345: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.346: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.346: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.346: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.347: [realtek] Enroll entering state 3 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.347: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.347: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.348: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.350: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.350: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.350: [realtek] Enroll entering state 4 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.350: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.350: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.351: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.351: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.352: Device reported finger status change: FP_FINGER_STATUS_NONE 163s (process:4354): libfprint-device-DEBUG: 03:38:30.352: Device reported enroll progress, reported 4 of 8 have been completed 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.352: [realtek] Enroll entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.352: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.352: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.352: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.353: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.353: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.353: [realtek] Enroll entering state 3 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.353: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.354: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.354: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.355: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.356: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.356: [realtek] Enroll entering state 4 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.356: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.356: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.356: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.357: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.357: Device reported finger status change: FP_FINGER_STATUS_NONE 163s (process:4354): libfprint-device-DEBUG: 03:38:30.357: Device reported enroll progress, reported 5 of 8 have been completed 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.357: [realtek] Enroll entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.357: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.357: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.358: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.358: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.358: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.359: [realtek] Enroll entering state 3 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.359: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.359: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.359: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.360: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.360: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.360: [realtek] Enroll entering state 4 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.360: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.361: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.362: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.363: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.363: Device reported finger status change: FP_FINGER_STATUS_NONE 163s (process:4354): libfprint-device-DEBUG: 03:38:30.363: Device reported enroll progress, reported 6 of 8 have been completed 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.363: [realtek] Enroll entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.363: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.363: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.364: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.364: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.364: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.364: [realtek] Enroll entering state 3 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.364: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.365: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.365: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.366: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.367: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.367: [realtek] Enroll entering state 4 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.367: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.367: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.367: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.368: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.368: Device reported finger status change: FP_FINGER_STATUS_NONE 163s (process:4354): libfprint-device-DEBUG: 03:38:30.368: Device reported enroll progress, reported 7 of 8 have been completed 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.368: [realtek] Enroll entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.368: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.368: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.369: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.369: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.369: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.370: [realtek] Enroll entering state 3 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.370: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.370: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.370: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.371: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.371: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.371: [realtek] Enroll entering state 4 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.371: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.372: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.373: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.374: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.374: Device reported finger status change: FP_FINGER_STATUS_NONE 163s (process:4354): libfprint-device-DEBUG: 03:38:30.374: Device reported enroll progress, reported 8 of 8 have been completed 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.374: [realtek] Enroll entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.374: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.374: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.374: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.375: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.375: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.375: [realtek] Enroll entering state 3 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.375: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.376: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.376: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.376: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.377: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.377: [realtek] Enroll entering state 4 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.377: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.377: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.378: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.378: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.379: Device reported finger status change: FP_FINGER_STATUS_NONE 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.379: [realtek] Enroll entering state 5 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.379: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.379: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.380: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.380: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.381: [realtek] Enroll entering state 6 163s (process:4354): libfprint-realtek-DEBUG: 03:38:30.381: user_id: FP1-00000000-0-00000000-nobody, finger: 0xff 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.381: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.381: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.382: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.382: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.383: [realtek] Enroll completed successfully 163s (process:4354): libfprint-realtek-DEBUG: 03:38:30.383: Enrollment complete! 163s (process:4354): libfprint-device-DEBUG: 03:38:30.383: Device reported enroll completion 163s (process:4354): libfprint-device-DEBUG: 03:38:30.383: Print for finger FP_FINGER_UNKNOWN enrolled 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.383: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-device-DEBUG: 03:38:30.383: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 163s (process:4354): libfprint-device-DEBUG: 03:38:30.383: Not updating temperature model, device can run continuously! 163s (process:4354): libfprint-realtek-DEBUG: 03:38:30.383: 110191060: ../libfprint/drivers/realtek/realtek.c:1345 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.383: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.384: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.384: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-realtek-DEBUG: 03:38:30.385: Query templates complete! 163s (process:4354): libfprint-device-DEBUG: 03:38:30.385: Device reported listing completion 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.385: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-device-DEBUG: 03:38:30.385: Completing action FPI_DEVICE_ACTION_LIST in idle! 163s (process:4354): libfprint-device-DEBUG: 03:38:30.385: Not updating temperature model, device can run continuously! 163s (process:4354): libfprint-device-DEBUG: 03:38:30.385: Not updating temperature model, device can run continuously! 163s (process:4354): libfprint-realtek-DEBUG: 03:38:30.385: 110193335: ../libfprint/drivers/realtek/realtek.c:1178 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.385: [realtek] Verify & Identify entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.385: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.386: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.387: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.390: [realtek] Verify & Identify entering state 1 163s (process:4354): libfprint-device-DEBUG: 03:38:30.390: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.390: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.391: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.391: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.391: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.391: [realtek] Verify & Identify entering state 2 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.391: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.392: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.392: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.393: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.393: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.393: [realtek] Verify & Identify entering state 3 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.393: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.393: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.394: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.395: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.396: Device reported finger status change: FP_FINGER_STATUS_NONE 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.396: [realtek] Verify & Identify entering state 4 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.396: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.396: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.397: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.397: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.398: Device reported verify result 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.398: [realtek] Verify & Identify entering state 5 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.398: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.398: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.398: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.398: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.399: [realtek] Verify & Identify completed successfully 163s (process:4354): libfprint-realtek-DEBUG: 03:38:30.399: Verify complete! 163s (process:4354): libfprint-device-DEBUG: 03:38:30.399: Device reported verify completion 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.399: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-device-DEBUG: 03:38:30.399: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 163s (process:4354): libfprint-device-DEBUG: 03:38:30.399: Not updating temperature model, device can run continuously! 163s (process:4354): libfprint-device-DEBUG: 03:38:30.399: Not updating temperature model, device can run continuously! 163s (process:4354): libfprint-realtek-DEBUG: 03:38:30.399: 110207516: ../libfprint/drivers/realtek/realtek.c:1178 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.399: [realtek] Verify & Identify entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.399: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.400: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.401: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.401: [realtek] Verify & Identify entering state 1 163s (process:4354): libfprint-device-DEBUG: 03:38:30.401: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.401: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.402: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.402: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.402: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.403: [realtek] Verify & Identify entering state 2 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.403: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.403: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.403: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.404: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.405: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.405: [realtek] Verify & Identify entering state 3 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.405: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.405: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.405: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.406: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.406: Device reported finger status change: FP_FINGER_STATUS_NONE 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.406: [realtek] Verify & Identify entering state 4 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.406: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.407: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.407: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.408: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-device-DEBUG: 03:38:30.408: Device reported identify result 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.408: [realtek] Verify & Identify completed successfully 163s (process:4354): libfprint-realtek-DEBUG: 03:38:30.408: Verify complete! 163s (process:4354): libfprint-device-DEBUG: 03:38:30.408: Device reported identify completion 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.408: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-device-DEBUG: 03:38:30.408: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 163s (process:4354): libfprint-device-DEBUG: 03:38:30.408: Not updating temperature model, device can run continuously! 163s (process:4354): libfprint-realtek-DEBUG: 03:38:30.409: 110216707: ../libfprint/drivers/realtek/realtek.c:1314 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.409: [realtek] Delete print entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.409: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.409: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.410: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.410: [realtek] Delete print entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.410: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.411: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.411: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.411: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.413: [realtek] Delete print completed successfully 163s (process:4354): libfprint-realtek-DEBUG: 03:38:30.413: Delete print complete! 163s (process:4354): libfprint-device-DEBUG: 03:38:30.413: Device reported deletion completion 163s (process:4354): libfprint-SSM-DEBUG: 03:38:30.413: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 163s (process:4354): libfprint-device-DEBUG: 03:38:30.413: Completing action FPI_DEVICE_ACTION_DELETE in idle! 163s (process:4354): libfprint-device-DEBUG: 03:38:30.413: Not updating temperature model, device can run continuously! 163s (process:4354): libfprint-realtek-DEBUG: 03:38:30.413: 110221004: ../libfprint/drivers/realtek/realtek.c:1302 163s (process:4354): libfprint-device-DEBUG: 03:38:30.413: Device reported close completion 163s (process:4354): libfprint-device-DEBUG: 03:38:30.413: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 163s (process:4354): libfprint-device-DEBUG: 03:38:30.413: Not updating temperature model, device can run continuously! 163s enrolling 163s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x70424858a340 (FpiDeviceRealtek at 0x339ec180)>, 1, None, None, None) 163s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x70424858a340 (FpiDeviceRealtek at 0x339ec180)>, 2, None, None, None) 163s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x70424858a340 (FpiDeviceRealtek at 0x339ec180)>, 3, None, None, None) 163s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x70424858a340 (FpiDeviceRealtek at 0x339ec180)>, 4, None, None, None) 163s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x70424858a340 (FpiDeviceRealtek at 0x339ec180)>, 5, None, None, None) 163s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x70424858a340 (FpiDeviceRealtek at 0x339ec180)>, 6, None, None, None) 163s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x70424858a340 (FpiDeviceRealtek at 0x339ec180)>, 7, None, None, None) 163s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x70424858a340 (FpiDeviceRealtek at 0x339ec180)>, 8, None, None, None) 163s enroll done 163s listing 163s listing done 163s verifying 163s verify done 163s async identifying 163s indentification_done: 163s deleting 163s delete done 163s ** (umockdev-run:4350): DEBUG: 03:38:30.430: umockdev.vala:154: Removing test bed /tmp/umockdev.DML212 163s (umockdev-run:4350): GLib-DEBUG: 03:38:30.436: unsetenv() is not thread-safe and should not be used after threads are created 163s PASS: libfprint-2/driver-realtek-5816.test 163s Running test: libfprint-2/fpi-ssm.test 163s TAP version 14 163s # random seed: R02Se347210021239b02b2f41cfc7b6597b5 163s 1..42 163s # Start of ssm tests 163s ok 1 /ssm/new 163s ok 2 /ssm/set_data 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 163s ok 3 /ssm/start 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 163s ok 4 /ssm/next 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 163s ok 5 /ssm/jump_to_state 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 163s ok 6 /ssm/mark_completed 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 163s # 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. 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 163s ok 7 /ssm/mark_failed 163s # Start of new tests 163s ok 8 /ssm/new/full 163s ok 9 /ssm/new/no_handler 163s ok 10 /ssm/new/wrong_states 163s # End of new tests 163s # Start of set_data tests 163s ok 11 /ssm/set_data/cleanup 163s # End of set_data tests 163s # Start of start tests 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM_SINGLE_STATE entering state 0 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM_SINGLE_STATE completed successfully 163s ok 12 /ssm/start/single 163s # End of start tests 163s # Start of next tests 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 163s ok 13 /ssm/next/complete 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 163s ok 14 /ssm/next/not_started 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 163s ok 15 /ssm/next/with_delayed 163s # End of next tests 163s # Start of jump_to_state tests 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 163s ok 16 /ssm/jump_to_state/not_started 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 163s ok 17 /ssm/jump_to_state/with_delayed 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 163s ok 18 /ssm/jump_to_state/last 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 14 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state -10 163s ok 19 /ssm/jump_to_state/wrong 163s # End of jump_to_state tests 163s # Start of mark_completed tests 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 163s ok 20 /ssm/mark_completed/not_started 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 163s ok 21 /ssm/mark_completed/with_delayed 163s # End of mark_completed tests 163s # Start of mark_failed tests 163s # 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. 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 163s ok 22 /ssm/mark_failed/not_started 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 163s # 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. 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 163s ok 23 /ssm/mark_failed/with_delayed 163s # End of mark_failed tests 163s # Start of delayed tests 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 163s ok 24 /ssm/delayed/next 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 163s ok 25 /ssm/delayed/jump_to_state 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 163s ok 26 /ssm/delayed/mark_completed 163s # Start of next tests 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 163s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 164s ok 27 /ssm/delayed/next/cancel 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 164s ok 28 /ssm/delayed/next/not_started 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 164s ok 29 /ssm/delayed/next/complete 164s # End of next tests 164s # Start of jump_to_state tests 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 164s ok 30 /ssm/delayed/jump_to_state/cancel 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 164s ok 31 /ssm/delayed/jump_to_state/not_started 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 164s ok 32 /ssm/delayed/jump_to_state/last 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 14 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state -10 164s ok 33 /ssm/delayed/jump_to_state/wrong 164s # End of jump_to_state tests 164s # Start of mark_completed tests 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 164s Executing: libfprint-2/fpi-ssm.test 164s ok 34 /ssm/delayed/mark_completed/cancel 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 164s ok 35 /ssm/delayed/mark_completed/not_started 164s # End of mark_completed tests 164s # Start of cancel tests 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 164s ok 36 /ssm/delayed/cancel/error 164s # End of cancel tests 164s # End of delayed tests 164s # Start of subssm tests 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 1 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 164s ok 37 /ssm/subssm/start 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 164s # 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. 164s # 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. 164s # 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. 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The device is still busy with another operation, please try again later. 164s ok 38 /ssm/subssm/mark_failed 164s # Start of start tests 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 164s ok 39 /ssm/subssm/start/with_started 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 164s ok 40 /ssm/subssm/start/with_delayed 164s # End of start tests 164s # End of subssm tests 164s # Start of cleanup tests 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 164s ok 41 /ssm/cleanup/complete 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 164s # libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 0 with error: non-cleanup 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 164s # libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 2 (cleanup) with error: cleanup 1 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 164s # libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 3 (cleanup) with error: cleanup 2 164s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: non-cleanup 164s ok 42 /ssm/cleanup/fail 164s # End of cleanup tests 164s # End of ssm tests 164s PASS: libfprint-2/fpi-ssm.test 164s Running test: libfprint-2/driver-goodixmoc.test 164s ** (umockdev-run:4364): DEBUG: 03:38:31.523: umockdev.vala:127: Created udev test bed /tmp/umockdev.VW0812 164s ** (umockdev-run:4364): DEBUG: 03:38:31.523: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3/3-9 164s ** (umockdev-run:4364): DEBUG: 03:38:31.525: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3/3-9 (subsystem usb) 164s ** (umockdev-run:4364): DEBUG: 03:38:31.529: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.VW0812/dev/bus/usb/003/004 164s ** (umockdev-run:4364): DEBUG: 03:38:31.529: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3 164s ** (umockdev-run:4364): DEBUG: 03:38:31.530: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3 (subsystem usb) 164s ** (umockdev-run:4364): DEBUG: 03:38:31.533: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.VW0812/dev/bus/usb/003/001 164s ** (umockdev-run:4364): DEBUG: 03:38:31.533: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 164s ** (umockdev-run:4364): DEBUG: 03:38:31.533: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 164s (process:4368): libfprint-context-DEBUG: 03:38:31.621: Initializing FpContext (libfprint version 1.94.8+tod1) 164s (process:4368): libfprint-tod-DEBUG: 03:38:31.621: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 164s (process:4368): libfprint-context-DEBUG: 03:38:31.623: No driver found for USB device 1D6B:0002 164s (process:4368): libfprint-device-DEBUG: 03:38:31.624: Device reported probe completion 164s (process:4368): libfprint-device-DEBUG: 03:38:31.625: Completing action FPI_DEVICE_ACTION_PROBE in idle! 164s (process:4368): libfprint-device-DEBUG: 03:38:31.625: Not updating temperature model, device can run continuously! 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.626: [goodixmoc] FP_INIT_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.626: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.627: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.627: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.628: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.629: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-goodixmoc-DEBUG: 03:38:31.629: Firmware type: APP 164s (process:4368): libfprint-goodixmoc-DEBUG: 03:38:31.629: Firmware version: 01000274 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.629: [goodixmoc] FP_INIT_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.629: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.630: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.630: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.631: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.631: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.632: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.633: [goodixmoc] FP_INIT_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.633: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.633: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.633: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.634: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.635: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.635: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.636: [goodixmoc] FP_INIT_NUM_STATES completed successfully 164s (process:4368): libfprint-device-DEBUG: 03:38:31.636: Device reported open completion 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.636: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-device-DEBUG: 03:38:31.636: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s (process:4368): libfprint-device-DEBUG: 03:38:31.636: Not updating temperature model, device can run continuously! 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.636: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.636: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.637: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.638: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.638: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-goodixmoc-DEBUG: 03:38:31.639: Successfully cleared storage 164s (process:4368): libfprint-device-DEBUG: 03:38:31.639: Device reported deletion completion 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.639: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-device-DEBUG: 03:38:31.639: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 164s (process:4368): libfprint-device-DEBUG: 03:38:31.639: Not updating temperature model, device can run continuously! 164s (process:4368): libfprint-device-DEBUG: 03:38:31.640: Not updating temperature model, device can run continuously! 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.640: [goodixmoc] enroll entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.640: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.640: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.641: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.641: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.642: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.645: [goodixmoc] enroll entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.645: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.646: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.646: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.647: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.647: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.648: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.649: [goodixmoc] enroll entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.649: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.650: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.650: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.650: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.651: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.652: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.652: [goodixmoc] enroll entering state 3 164s (process:4368): libfprint-device-DEBUG: 03:38:31.652: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.652: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.653: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.653: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.654: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.654: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.655: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.655: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.655: [goodixmoc] enroll entering state 4 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.655: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.657: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.657: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.658: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.659: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.659: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.660: Device reported enroll progress, reported 1 of 12 have been completed 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.660: [goodixmoc] enroll entering state 5 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.660: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.660: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.661: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.661: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.662: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.662: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.663: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.663: [goodixmoc] enroll entering state 3 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.663: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.664: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.664: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.665: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.665: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.666: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.666: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.666: [goodixmoc] enroll entering state 4 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.666: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.667: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.667: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.668: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.668: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.669: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.670: Device reported enroll progress, reported 2 of 12 have been completed 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.670: [goodixmoc] enroll entering state 5 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.670: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.670: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.671: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.671: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.672: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.673: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.673: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.673: [goodixmoc] enroll entering state 3 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.673: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.674: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.674: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.675: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.675: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.676: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.676: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.676: [goodixmoc] enroll entering state 4 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.676: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.677: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.677: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.678: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.678: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.679: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.679: Device reported enroll progress, reported 3 of 12 have been completed 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.680: [goodixmoc] enroll entering state 5 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.680: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.680: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.680: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.681: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.681: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.682: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.683: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.683: [goodixmoc] enroll entering state 3 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.683: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.683: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.683: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.684: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.685: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.685: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.686: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.686: [goodixmoc] enroll entering state 4 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.686: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.686: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.687: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.687: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.688: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.688: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.689: Device reported enroll progress, reported 4 of 12 have been completed 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.689: [goodixmoc] enroll entering state 5 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.689: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.690: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.690: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.691: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.692: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.693: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.693: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.693: [goodixmoc] enroll entering state 3 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.693: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.694: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.694: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.695: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.695: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.696: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.697: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.697: [goodixmoc] enroll entering state 4 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.697: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.697: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.697: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.698: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.699: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.699: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.700: Device reported enroll progress, reported 5 of 12 have been completed 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.700: [goodixmoc] enroll entering state 5 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.700: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.700: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.701: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.701: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.702: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.703: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.704: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.704: [goodixmoc] enroll entering state 3 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.704: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.704: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.704: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.705: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.705: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.706: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.707: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.707: [goodixmoc] enroll entering state 4 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.707: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.707: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.707: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.708: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.709: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.710: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.711: Device reported enroll progress, reported 6 of 12 have been completed 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.711: [goodixmoc] enroll entering state 5 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.711: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.711: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.711: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.712: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.712: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.713: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.714: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.714: [goodixmoc] enroll entering state 3 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.714: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.714: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.715: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.715: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.717: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.718: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.718: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.718: [goodixmoc] enroll entering state 4 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.718: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.719: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.719: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.720: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.720: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.721: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.721: Device reported enroll progress, reported 7 of 12 have been completed 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.722: [goodixmoc] enroll entering state 5 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.722: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.722: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.722: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.723: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.723: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.724: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.725: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.725: [goodixmoc] enroll entering state 3 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.725: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.725: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.725: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.727: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.728: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.729: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.729: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.729: [goodixmoc] enroll entering state 4 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.729: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.730: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.730: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.730: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.731: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.731: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.732: Device reported enroll progress, reported 8 of 12 have been completed 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.732: [goodixmoc] enroll entering state 5 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.732: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.732: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.733: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.733: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.734: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.734: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.735: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.735: [goodixmoc] enroll entering state 3 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.735: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.735: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.736: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.736: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.737: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.737: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.738: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.738: [goodixmoc] enroll entering state 4 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.738: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.738: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.739: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.739: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.740: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.740: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.741: Device reported enroll progress, reported 9 of 12 have been completed 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.741: [goodixmoc] enroll entering state 5 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.741: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.741: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.742: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.742: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.743: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.743: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.744: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.744: [goodixmoc] enroll entering state 3 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.744: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.744: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.745: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.745: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.746: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.747: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.747: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.747: [goodixmoc] enroll entering state 4 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.747: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.748: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.748: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.748: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.749: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.750: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.750: Device reported enroll progress, reported 10 of 12 have been completed 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.750: [goodixmoc] enroll entering state 5 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.750: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.751: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.751: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.752: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.752: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.753: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.753: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.753: [goodixmoc] enroll entering state 3 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.753: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.754: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.754: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.757: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.758: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.758: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.759: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.759: [goodixmoc] enroll entering state 4 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.759: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.759: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.760: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.760: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.761: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.762: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.762: Device reported enroll progress, reported 11 of 12 have been completed 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.762: [goodixmoc] enroll entering state 5 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.762: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.763: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.763: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.764: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.764: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.765: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.766: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.766: [goodixmoc] enroll entering state 3 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.766: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.766: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.766: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.767: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.767: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.768: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.769: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.769: [goodixmoc] enroll entering state 4 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.769: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.769: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.769: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.770: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.771: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.771: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.772: Device reported enroll progress, reported 12 of 12 have been completed 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.772: [goodixmoc] enroll entering state 6 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.772: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.772: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.772: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.773: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.773: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.775: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.775: [goodixmoc] enroll entering state 7 164s (process:4368): libfprint-goodixmoc-DEBUG: 03:38:31.775: user_id: FP1-00000000-0-00000000-nobody, user_id_len: 30, finger: 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.775: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.776: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.776: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.777: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.778: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.778: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.779: [goodixmoc] enroll entering state 8 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.779: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.779: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.780: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.780: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.781: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.782: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.785: [goodixmoc] enroll completed successfully 164s (process:4368): libfprint-goodixmoc-DEBUG: 03:38:31.785: Enrollment complete! 164s (process:4368): libfprint-device-DEBUG: 03:38:31.785: Device reported enroll completion 164s (process:4368): libfprint-device-DEBUG: 03:38:31.785: Device reported finger status change: FP_FINGER_STATUS_NONE 164s (process:4368): libfprint-device-DEBUG: 03:38:31.785: Print for finger FP_FINGER_UNKNOWN enrolled 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.785: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-device-DEBUG: 03:38:31.785: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 164s (process:4368): libfprint-device-DEBUG: 03:38:31.785: Not updating temperature model, device can run continuously! 164s (process:4368): libfprint-goodixmoc-DEBUG: 03:38:31.785: 111593536: ../libfprint/drivers/goodixmoc/goodix.c:1539 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.785: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.786: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.787: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.787: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.788: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-goodixmoc-DEBUG: 03:38:31.788: Query complete! 164s (process:4368): libfprint-device-DEBUG: 03:38:31.789: Device reported listing completion 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.789: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-device-DEBUG: 03:38:31.789: Completing action FPI_DEVICE_ACTION_LIST in idle! 164s (process:4368): libfprint-device-DEBUG: 03:38:31.789: Not updating temperature model, device can run continuously! 164s (process:4368): libfprint-device-DEBUG: 03:38:31.789: Not updating temperature model, device can run continuously! 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.789: [goodixmoc] verify entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.789: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.793: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.794: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.797: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.798: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.798: [goodixmoc] verify entering state 1 164s (process:4368): libfprint-device-DEBUG: 03:38:31.798: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.798: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.799: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.799: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.800: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.800: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.801: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.801: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.801: [goodixmoc] verify entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.802: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.802: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.802: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.803: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.803: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.804: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-DEBUG: 03:38:31.804: match, score: 28, study: 0 164s (process:4368): libfprint-device-DEBUG: 03:38:31.805: Device reported verify result 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.805: [goodixmoc] verify entering state 3 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.805: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.805: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.805: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.806: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.806: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.807: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.807: [goodixmoc] verify completed successfully 164s (process:4368): libfprint-goodixmoc-DEBUG: 03:38:31.808: Verify complete! 164s (process:4368): libfprint-device-DEBUG: 03:38:31.808: Device reported verify completion 164s (process:4368): libfprint-device-DEBUG: 03:38:31.808: Device reported finger status change: FP_FINGER_STATUS_NONE 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.808: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-device-DEBUG: 03:38:31.808: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 164s (process:4368): libfprint-device-DEBUG: 03:38:31.808: Not updating temperature model, device can run continuously! 164s (process:4368): libfprint-device-DEBUG: 03:38:31.808: Not updating temperature model, device can run continuously! 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.808: [goodixmoc] verify entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.808: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.809: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.809: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.810: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.811: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.811: [goodixmoc] verify entering state 1 164s (process:4368): libfprint-device-DEBUG: 03:38:31.811: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.811: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.812: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.812: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.812: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.813: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.814: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-device-DEBUG: 03:38:31.814: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.814: [goodixmoc] verify entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.814: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.815: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.815: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.816: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.816: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.817: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-DEBUG: 03:38:31.817: match, score: 35, study: 0 164s (process:4368): libfprint-device-DEBUG: 03:38:31.818: Device reported identify result 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.818: [goodixmoc] verify entering state 3 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.818: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.818: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.818: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.819: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.819: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.820: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.821: [goodixmoc] verify completed successfully 164s (process:4368): libfprint-goodixmoc-DEBUG: 03:38:31.821: Verify complete! 164s (process:4368): libfprint-device-DEBUG: 03:38:31.821: Device reported identify completion 164s (process:4368): libfprint-device-DEBUG: 03:38:31.821: Device reported finger status change: FP_FINGER_STATUS_NONE 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.821: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-device-DEBUG: 03:38:31.821: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 164s (process:4368): libfprint-device-DEBUG: 03:38:31.821: Not updating temperature model, device can run continuously! 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.821: [goodixmoc] FP_CMD_NUM_STATES entering state 0 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.822: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.822: [goodixmoc] FP_CMD_NUM_STATES entering state 1 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.823: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.823: [goodixmoc] FP_CMD_NUM_STATES entering state 2 164s (process:4368): libfprint-goodixmoc-DEBUG: 03:38:31.824: Successfully deleted enrolled user 164s (process:4368): libfprint-device-DEBUG: 03:38:31.824: Device reported deletion completion 164s (process:4368): libfprint-SSM-DEBUG: 03:38:31.824: [goodixmoc] FP_CMD_NUM_STATES completed successfully 164s (process:4368): libfprint-device-DEBUG: 03:38:31.824: Completing action FPI_DEVICE_ACTION_DELETE in idle! 164s (process:4368): libfprint-device-DEBUG: 03:38:31.824: Not updating temperature model, device can run continuously! 164s (process:4368): libfprint-device-DEBUG: 03:38:31.824: Device reported close completion 164s (process:4368): libfprint-device-DEBUG: 03:38:31.825: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 164s (process:4368): libfprint-device-DEBUG: 03:38:31.825: Not updating temperature model, device can run continuously! 164s enrolling 164s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x65c3c9889e80 (FpiDeviceGoodixMoc at 0x11560350)>, 1, None, None, None) 164s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x65c3c9889e80 (FpiDeviceGoodixMoc at 0x11560350)>, 2, None, None, None) 164s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x65c3c9889e80 (FpiDeviceGoodixMoc at 0x11560350)>, 3, None, None, None) 164s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x65c3c9889e80 (FpiDeviceGoodixMoc at 0x11560350)>, 4, None, None, None) 164s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x65c3c9889e80 (FpiDeviceGoodixMoc at 0x11560350)>, 5, None, None, None) 164s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x65c3c9889e80 (FpiDeviceGoodixMoc at 0x11560350)>, 6, None, None, None) 164s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x65c3c9889e80 (FpiDeviceGoodixMoc at 0x11560350)>, 7, None, None, None) 164s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x65c3c9889e80 (FpiDeviceGoodixMoc at 0x11560350)>, 8, None, None, None) 164s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x65c3c9889e80 (FpiDeviceGoodixMoc at 0x11560350)>, 9, None, None, None) 164s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x65c3c9889e80 (FpiDeviceGoodixMoc at 0x11560350)>, 10, None, None, None) 164s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x65c3c9889e80 (FpiDeviceGoodixMoc at 0x11560350)>, 11, None, None, None) 164s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x65c3c9889e80 (FpiDeviceGoodixMoc at 0x11560350)>, 12, None, None, None) 164s enroll done 164s listing 164s listing done 164s verifying 164s verify done 164s async identifying 164s indentification_done: 164s deleting 164s delete done 164s ** (umockdev-run:4364): DEBUG: 03:38:31.837: umockdev.vala:154: Removing test bed /tmp/umockdev.VW0812 164s (umockdev-run:4364): GLib-DEBUG: 03:38:31.843: unsetenv() is not thread-safe and should not be used after threads are created 164s PASS: libfprint-2/driver-goodixmoc.test 164s Running test: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_current.test 164s (process:4374): libfprint-context-DEBUG: 03:38:31.853: Initializing FpContext (libfprint version 1.94.8+tod1) 164s (process:4374): libfprint-tod-DEBUG: 03:38:31.854: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 164s (process:4374): libfprint-tod-DEBUG: 03:38:31.854: Found TOD entry point symbol 0x653c497c35d0, GType is 30039534916560 164s (process:4374): libfprint-tod-DEBUG: 03:38:31.854: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 164s (process:4374): libfprint-context-DEBUG: 03:38:31.857: No driver found for USB device 1D6B:0003 164s (process:4374): libfprint-context-DEBUG: 03:38:31.857: No driver found for USB device 0627:0001 164s (process:4374): libfprint-context-DEBUG: 03:38:31.857: No driver found for USB device 0627:0001 164s (process:4374): libfprint-context-DEBUG: 03:38:31.857: No driver found for USB device 1D6B:0002 164s (process:4374): libfprint-context-DEBUG: 03:38:31.857: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 164s (process:4374): libfprint-context-DEBUG: 03:38:31.857: created 164s (process:4374): libfprint-fake_test_dev_tod_current-DEBUG: 03:38:31.858: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 164s 164s (process:4374): libfprint-device-DEBUG: 03:38:31.858: Device reported probe completion 164s (process:4374): libfprint-device-DEBUG: 03:38:31.858: Completing action FPI_DEVICE_ACTION_PROBE in idle! 164s (process:4374): libfprint-device-DEBUG: 03:38:31.859: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s (/usr/libexec/installed-tests/libfprint-2/test-fpi-device-tod:4374): GLib-DEBUG: 03:38:31.859: setenv()/putenv() are not thread-safe and should not be used after threads are created 164s TAP version 14 164s # random seed: R02S0e7e11c701052cc31f70e52cf1bda9e2 164s 1..97 164s # Start of driver tests 164s ok 1 /driver/get_driver 164s ok 2 /driver/get_device_id 164s ok 3 /driver/get_name 164s # libfprint-fake_test_dev_tod_current-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_tod_current-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 4 /driver/is_open 164s ok 5 /driver/get_nr_enroll_stages 164s ok 6 /driver/set_nr_enroll_stages 164s ok 7 /driver/supports_identify 164s ok 8 /driver/supports_capture 164s ok 9 /driver/has_storage 164s ok 10 /driver/do_not_support_identify 164s ok 11 /driver/do_not_support_capture 164s ok 12 /driver/has_not_storage 164s ok 13 /driver/get_usb_device 164s ok 14 /driver/get_virtual_env 164s ok 15 /driver/get_driver_data 164s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 164s # libfprint-device-DEBUG: Tod version info is 'current' 164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 164s # 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: Getting TOD version for driver 'fake_test_dev_tod_current' 164s # libfprint-device-DEBUG: Tod version info is 'current' 164s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 164s # libfprint-device-DEBUG: Tod version info is 'current' 164s ok 16 /driver/initial_features 164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Probed device name in action FPI_DEVICE_ACTION_PROBE 164s # 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 ok 17 /driver/probe 164s # libfprint-fake_test_dev_tod_current-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_tod_current-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 18 /driver/open 164s # libfprint-fake_test_dev_tod_current-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_tod_current-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 19 /driver/close 164s # libfprint-fake_test_dev_tod_current-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_tod_current-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: Print for finger FP_FINGER_UNKNOWN enrolled 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-fake_test_dev_tod_current-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 20 /driver/enroll 164s # libfprint-fake_test_dev_tod_current-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_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 164s # 164s # libfprint-device-DEBUG: Device reported verify result 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_COLD -> FP_TEMPERATURE_WARM 164s # libfprint-fake_test_dev_tod_current-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 21 /driver/verify 164s # libfprint-fake_test_dev_tod_current-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_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 164s # 164s # libfprint-device-DEBUG: Device reported identify result 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.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 164s # libfprint-fake_test_dev_tod_current-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 22 /driver/identify 164s # libfprint-fake_test_dev_tod_current-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_tod_current-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_tod_current-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 23 /driver/capture 164s # libfprint-fake_test_dev_tod_current-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_tod_current-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_tod_current-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 24 /driver/list 164s # libfprint-fake_test_dev_tod_current-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_tod_current-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_tod_current-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 25 /driver/delete 164s # libfprint-fake_test_dev_tod_current-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: Getting TOD version for driver 'fake_test_dev_tod_current' 164s # libfprint-device-DEBUG: Tod version info is 'current' 164s # libfprint-fake_test_dev_tod_current-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_tod_current-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 26 /driver/clear_storage 164s # libfprint-fake_test_dev_tod_current-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: Idle cancelling on ongoing operation! 164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 164s # 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 165s # 165s # libfprint-device-DEBUG: Device reported deletion completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 165s # 165s # libfprint-device-DEBUG: Device reported close completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s ok 27 /driver/cancel 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 165s # 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 165s # libfprint-device-DEBUG: Tod version info is 'current' 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 165s # 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 165s # 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 165s # 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 165s # 165s # libfprint-device-DEBUG: Device reported verify result 165s # libfprint-device-DEBUG: Device reported verify completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 165s # 165s # libfprint-device-DEBUG: Device reported close completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 165s ok 28 /driver/critical 165s ok 29 /driver/get_current_action 165s ok 30 /driver/timeout 165s ok 31 /driver/error_types 165s ok 32 /driver/retry_error_types 165s # Start of get_scan_type tests 165s ok 33 /driver/get_scan_type/press 165s ok 34 /driver/get_scan_type/swipe 165s # End of get_scan_type tests 165s # Start of set_scan_type tests 165s ok 35 /driver/set_scan_type/press 165s ok 36 /driver/set_scan_type/swipe 165s # End of set_scan_type tests 165s # Start of finger_status tests 165s ok 37 /driver/finger_status/inactive 165s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 165s ok 38 /driver/finger_status/waiting 165s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 165s ok 39 /driver/finger_status/present 165s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 165s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 165s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 165s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE 165s ok 40 /driver/finger_status/changes 165s # End of finger_status tests 165s # Start of features tests 165s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 165s # libfprint-device-DEBUG: Tod version info is 'current' 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 165s # 165s # libfprint-device-DEBUG: Device reported probe completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s ok 41 /driver/features/probe_updates 165s # End of features tests 165s # Start of initial_features tests 165s ok 42 /driver/initial_features/none 165s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 165s # libfprint-device-DEBUG: Tod version info is 'current' 165s ok 43 /driver/initial_features/no_capture 165s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 165s # libfprint-device-DEBUG: Tod version info is 'current' 165s ok 44 /driver/initial_features/no_verify 165s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 165s # libfprint-device-DEBUG: Tod version info is 'current' 165s ok 45 /driver/initial_features/no_identify 165s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 165s # libfprint-device-DEBUG: Tod version info is 'current' 165s ok 46 /driver/initial_features/no_storage 165s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 165s # libfprint-device-DEBUG: Tod version info is 'current' 165s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 165s # libfprint-device-DEBUG: Tod version info is 'current' 165s ok 47 /driver/initial_features/no_list 165s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 165s # libfprint-device-DEBUG: Tod version info is 'current' 165s ok 48 /driver/initial_features/no_delete 165s ok 49 /driver/initial_features/no_clear 165s # End of initial_features tests 165s # Start of probe tests 165s # libfprint-device-DEBUG: Device reported probe completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s ok 50 /driver/probe/error 165s # libfprint-device-DEBUG: Device reported generic error (The operation is not supported on this device!) during action; action was: FPI_DEVICE_ACTION_PROBE 165s # libfprint-device-DEBUG: Device reported probe completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s ok 51 /driver/probe/action_error 165s # End of probe tests 165s # Start of open tests 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 165s # 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s ok 52 /driver/open/error 165s # End of open tests 165s # Start of close tests 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 165s # 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 165s # 165s # libfprint-device-DEBUG: Device reported close completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s ok 53 /driver/close/error 165s # End of close tests 165s # Start of enroll tests 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 165s # 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 165s # 165s # libfprint-device-DEBUG: Device reported enroll completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 165s # 165s # libfprint-device-DEBUG: Device reported close completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 165s ok 54 /driver/enroll/error 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 165s # 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-device-DEBUG: Device reported enroll progress, reported 1277146001 of 757883502 have been completed 165s # libfprint-device-DEBUG: Device reported enroll progress, reported 1458694427 of 757883502 have been completed 165s # libfprint-device-DEBUG: Device reported enroll progress, reported 1998083870 of 757883502 have been completed 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 165s # 165s # libfprint-device-DEBUG: Device reported enroll completion 165s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 165s # 165s # libfprint-device-DEBUG: Device reported close completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 165s ok 55 /driver/enroll/progress 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 165s # 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 165s # 165s # libfprint-device-DEBUG: Device reported enroll completion 165s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 165s # 165s # libfprint-device-DEBUG: Device reported close completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 165s ok 56 /driver/enroll/update_nbis 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 165s # 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 165s # 165s # libfprint-device-DEBUG: Device reported close completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s ok 57 /driver/enroll/update_nbis_wrong_device 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 165s # 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 165s # 165s # libfprint-device-DEBUG: Device reported close completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s ok 58 /driver/enroll/update_nbis_wrong_driver 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 165s # 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 165s # 165s # libfprint-device-DEBUG: Device reported close completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s ok 59 /driver/enroll/update_nbis_missing_feature 165s # Start of error tests 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 165s # 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-device-DEBUG: Device reported enroll completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 165s # libfprint-device-DEBUG: Device reported enroll completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 165s # libfprint-device-DEBUG: Device reported enroll completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 165s # 165s # libfprint-device-DEBUG: Device reported close completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 165s ok 60 /driver/enroll/error/no_print 165s # End of error tests 165s # End of enroll tests 165s # Start of verify tests 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 165s # 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 165s # 165s # libfprint-device-DEBUG: Device reported verify result 165s # libfprint-device-DEBUG: Device reported verify completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 165s # 165s # libfprint-device-DEBUG: Device reported close completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 165s ok 61 /driver/verify/fail 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 165s # 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 165s # 165s # libfprint-device-DEBUG: Device reported verify result 165s # libfprint-device-DEBUG: Device reported verify completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 165s # 165s # libfprint-device-DEBUG: Device reported close completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 165s ok 62 /driver/verify/retry 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 165s # 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 165s # 165s # libfprint-device-DEBUG: Device reported verify completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 165s # 165s # libfprint-device-DEBUG: Device reported close completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 165s ok 63 /driver/verify/error 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 165s # 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 165s # 165s # libfprint-device-DEBUG: Device reported close completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s ok 64 /driver/verify/not_supported 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 165s # 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-device-DEBUG: Device reported verify result 165s # libfprint-device-DEBUG: Device reported verify completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 165s # 165s # libfprint-device-DEBUG: Device reported close completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 165s ok 65 /driver/verify/report_no_cb 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 165s # 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-device-DEBUG: Device reported verify completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 165s # 165s # libfprint-device-DEBUG: Device reported close completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 165s ok 66 /driver/verify/not_reported 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 165s # 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-device-DEBUG: Device reported verify result 165s # libfprint-device-DEBUG: Device reported verify completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 165s # libfprint-device-DEBUG: Device reported verify result 165s # libfprint-device-DEBUG: Device reported verify completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 165s # libfprint-device-DEBUG: Device reported verify result 165s # libfprint-device-DEBUG: Device reported verify completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 165s # libfprint-device-DEBUG: Device reported verify result 165s # libfprint-device-DEBUG: Device reported verify completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 165s # libfprint-device-DEBUG: Device reported verify result 165s # libfprint-device-DEBUG: Device reported verify completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 165s # 165s # libfprint-device-DEBUG: Device reported close completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 165s ok 67 /driver/verify/complete_retry 165s # End of verify tests 165s # Start of identify tests 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 165s # 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 165s # 165s # libfprint-device-DEBUG: Device reported identify result 165s # libfprint-device-DEBUG: Device reported identify completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 165s # 165s # libfprint-device-DEBUG: Device reported close completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 165s ok 68 /driver/identify/fail 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 165s # 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 165s # 165s # libfprint-device-DEBUG: Device reported identify result 165s # libfprint-device-DEBUG: Device reported identify completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 165s # 165s # libfprint-device-DEBUG: Device reported close completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 165s ok 69 /driver/identify/retry 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 165s # 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 165s # 165s # libfprint-device-DEBUG: Device reported identify completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 165s # 165s # libfprint-device-DEBUG: Device reported close completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 165s ok 70 /driver/identify/error 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 165s # 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-device-DEBUG: Device reported identify completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 165s # 165s # libfprint-device-DEBUG: Device reported close completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s ok 71 /driver/identify/not_reported 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 165s # 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-device-DEBUG: Device reported identify result 165s # libfprint-device-DEBUG: Device reported identify completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 165s # libfprint-device-DEBUG: Device reported identify result 165s # libfprint-device-DEBUG: Device reported identify completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 165s # libfprint-device-DEBUG: Device reported identify result 165s # libfprint-device-DEBUG: Device reported identify completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 165s # 165s # libfprint-device-DEBUG: Device reported close completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 165s ok 72 /driver/identify/complete_retry 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 165s # 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-device-DEBUG: Device reported identify result 165s # libfprint-device-DEBUG: Device reported identify completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 165s # 165s # libfprint-device-DEBUG: Device reported close completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 165s ok 73 /driver/identify/report_no_cb 165s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 165s # libfprint-device-DEBUG: Tod version info is 'current' 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 165s # 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 165s # 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 165s # 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 165s # 165s # libfprint-device-DEBUG: Device reported identify result 165s # libfprint-device-DEBUG: Device reported identify completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 165s # 165s # libfprint-device-DEBUG: Device reported close completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 165s ok 74 /driver/identify/suspend_continues 165s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 165s # libfprint-device-DEBUG: Tod version info is 'current' 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 165s # 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 165s # 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 165s # 165s # libfprint-device-DEBUG: Device reported identify result 165s # libfprint-device-DEBUG: Device reported identify completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 165s # 165s # libfprint-device-DEBUG: Device reported close completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 165s ok 75 /driver/identify/suspend_succeeds 165s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 165s # libfprint-device-DEBUG: Tod version info is 'current' 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 165s # 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 165s # 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 165s # 165s # libfprint-device-DEBUG: Device reported identify completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 165s # 165s # libfprint-device-DEBUG: Device reported close completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 165s ok 76 /driver/identify/suspend_busy_error 165s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 165s # libfprint-device-DEBUG: Tod version info is 'current' 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 165s # 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 165s # 165s # libfprint-device-DEBUG: Device reported close completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s ok 77 /driver/identify/suspend_while_idle 165s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 165s # libfprint-device-DEBUG: Tod version info is 'current' 165s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 165s # 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.30, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 167s # libfprint-device-DEBUG: Updated temperature model after 2.00 seconds, ratio 0.30 -> 0.74, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_HOT 167s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 167s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 167s # 167s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 167s # 167s # libfprint-device-DEBUG: Device reported identify completion 167s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 167s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 167s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 1 -> 1, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 167s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 169s Executing: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_current.test 169s # libfprint-device-DEBUG: Updated temperature model after 2.09 seconds, ratio 0.74 -> 0.49, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_WARM 172s # libfprint-device-DEBUG: Updated temperature model after 3.10 seconds, ratio 0.49 -> 0.26, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 172s # 172s # libfprint-device-DEBUG: Device reported close completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.26 -> 0.26, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s ok 78 /driver/identify/warmup_cooldown 172s # slow test /driver/identify/warmup_cooldown executed in 7.30 secs 172s # End of identify tests 172s # Start of capture tests 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 172s # 172s # libfprint-device-DEBUG: Device reported open completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 172s # 172s # libfprint-device-DEBUG: Device reported close completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s ok 79 /driver/capture/not_supported 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 172s # 172s # libfprint-device-DEBUG: Device reported open completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 172s # 172s # libfprint-device-DEBUG: Device reported capture completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 172s # 172s # libfprint-device-DEBUG: Device reported close completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s ok 80 /driver/capture/error 172s # End of capture tests 172s # Start of list tests 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 172s # 172s # libfprint-device-DEBUG: Device reported open completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 172s # 172s # libfprint-device-DEBUG: Device reported listing completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 172s # 172s # libfprint-device-DEBUG: Device reported close completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s ok 81 /driver/list/error 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 172s # 172s # libfprint-device-DEBUG: Device reported open completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 172s # 172s # libfprint-device-DEBUG: Device reported close completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s ok 82 /driver/list/no_storage 172s # End of list tests 172s # Start of delete tests 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 172s # 172s # libfprint-device-DEBUG: Device reported open completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 172s # 172s # libfprint-device-DEBUG: Device reported deletion completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 172s # 172s # libfprint-device-DEBUG: Device reported close completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s ok 83 /driver/delete/error 172s # End of delete tests 172s # Start of clear_storage tests 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 172s # 172s # libfprint-device-DEBUG: Device reported open completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 172s # libfprint-device-DEBUG: Tod version info is 'current' 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 172s # 172s # libfprint-device-DEBUG: Device reported deletion completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 172s # 172s # libfprint-device-DEBUG: Device reported close completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s ok 84 /driver/clear_storage/error 172s # End of clear_storage tests 172s # Start of cancel tests 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 172s # 172s # libfprint-device-DEBUG: Device reported open completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 172s # 172s # libfprint-device-DEBUG: Device reported deletion completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 172s # 172s # libfprint-device-DEBUG: Device reported close completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s ok 85 /driver/cancel/fail 172s # End of cancel tests 172s # Start of get_current_action tests 172s # libfprint-device-DEBUG: Device reported open completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 172s # 172s # libfprint-device-DEBUG: Device reported close completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s ok 86 /driver/get_current_action/open 172s # End of get_current_action tests 172s # Start of get_cancellable tests 172s ok 87 /driver/get_cancellable/error 172s # libfprint-device-DEBUG: Device reported open completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 172s # 172s # libfprint-device-DEBUG: Device reported close completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s ok 88 /driver/get_cancellable/open 172s # Start of open tests 172s # libfprint-device-DEBUG: Device reported open completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 172s # 172s # libfprint-device-DEBUG: Device reported close completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s ok 89 /driver/get_cancellable/open/internal 172s # End of open tests 172s # End of get_cancellable tests 172s # Start of action_is_cancelled tests 172s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 172s # libfprint-device-DEBUG: Tod version info is 'current' 172s # libfprint-device-DEBUG: Device reported open completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 172s # 172s # libfprint-device-DEBUG: Device reported close completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s ok 90 /driver/action_is_cancelled/open 172s ok 91 /driver/action_is_cancelled/error 172s # Start of open tests 172s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 172s # libfprint-device-DEBUG: Tod version info is 'current' 172s # libfprint-device-DEBUG: Device reported open completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 172s # 172s # libfprint-device-DEBUG: Device reported close completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s ok 92 /driver/action_is_cancelled/open/internal 172s # End of open tests 172s # End of action_is_cancelled tests 172s # Start of complete_action tests 172s # Start of all tests 172s ok 93 /driver/complete_action/all/error 172s # End of all tests 172s # End of complete_action tests 172s # Start of action_error tests 172s ok 94 /driver/action_error/error 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 172s # 172s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_OPEN 172s # libfprint-device-DEBUG: Device reported open completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 172s # 172s # libfprint-device-DEBUG: Device reported open completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 172s # 172s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_ENROLL 172s # libfprint-device-DEBUG: Device reported enroll completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 172s # 172s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_VERIFY 172s # libfprint-device-DEBUG: Device reported verify completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 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 generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 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.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 172s # 172s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CAPTURE 172s # libfprint-device-DEBUG: Device reported capture completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 172s # 172s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_LIST 172s # libfprint-device-DEBUG: Device reported listing completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 172s # 172s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_DELETE 172s # libfprint-device-DEBUG: Device reported deletion completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 172s # libfprint-device-DEBUG: Tod version info is 'current' 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 172s # 172s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLEAR_STORAGE 172s # libfprint-device-DEBUG: Device reported deletion completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 172s # 172s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLOSE 172s # libfprint-device-DEBUG: Device reported close completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s ok 95 /driver/action_error/all 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 172s # 172s # libfprint-device-DEBUG: Device reported open completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 172s # 172s # libfprint-device-DEBUG: Device reported open completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 172s # 172s # libfprint-device-DEBUG: Device reported enroll completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 172s # 172s # libfprint-device-DEBUG: Device reported verify completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 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.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 172s # 172s # libfprint-device-DEBUG: Device reported capture completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 172s # 172s # libfprint-device-DEBUG: Device reported listing completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 172s # 172s # libfprint-device-DEBUG: Device reported deletion completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 172s # libfprint-device-DEBUG: Tod version info is 'current' 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 172s # 172s # libfprint-device-DEBUG: Device reported deletion completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 172s # 172s # libfprint-device-DEBUG: Device reported close completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s ok 96 /driver/action_error/fail 172s # End of action_error tests 172s # Start of timeout tests 172s ok 97 /driver/timeout/cancelled 172s # End of timeout tests 172s # End of driver tests 172s PASS: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_current.test 172s Running test: libfprint-2/driver-vfs301.test 172s ** (umockdev-run:4382): DEBUG: 03:38:39.570: umockdev.vala:127: Created udev test bed /tmp/umockdev.6WMD22 172s ** (umockdev-run:4382): DEBUG: 03:38:39.571: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3 172s ** (umockdev-run:4382): DEBUG: 03:38:39.572: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3 (subsystem usb) 172s ** (umockdev-run:4382): DEBUG: 03:38:39.575: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.6WMD22/dev/bus/usb/002/005 172s ** (umockdev-run:4382): DEBUG: 03:38:39.575: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1d.0/usb2/2-1 172s ** (umockdev-run:4382): DEBUG: 03:38:39.577: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1d.0/usb2/2-1 (subsystem usb) 172s ** (umockdev-run:4382): DEBUG: 03:38:39.579: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.6WMD22/dev/bus/usb/002/002 172s ** (umockdev-run:4382): DEBUG: 03:38:39.579: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1d.0/usb2 172s ** (umockdev-run:4382): DEBUG: 03:38:39.580: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1d.0/usb2 (subsystem usb) 172s ** (umockdev-run:4382): DEBUG: 03:38:39.583: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.6WMD22/dev/bus/usb/002/001 172s ** (umockdev-run:4382): DEBUG: 03:38:39.584: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1d.0 172s ** (umockdev-run:4382): DEBUG: 03:38:39.584: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1d.0 (subsystem pci) 172s (umockdev-run:4382): GLib-GIO-DEBUG: 03:38:39.587: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 172s (process:4386): libfprint-context-DEBUG: 03:38:39.694: Initializing FpContext (libfprint version 1.94.8+tod1) 172s (process:4386): libfprint-tod-DEBUG: 03:38:39.695: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 172s (process:4386): libfprint-context-DEBUG: 03:38:39.697: No driver found for USB device 8087:0020 172s (process:4386): libfprint-context-DEBUG: 03:38:39.697: No driver found for USB device 1D6B:0002 172s (process:4386): libfprint-device-DEBUG: 03:38:39.698: Device reported probe completion 172s (process:4386): libfprint-device-DEBUG: 03:38:39.698: Completing action FPI_DEVICE_ACTION_PROBE in idle! 172s (process:4386): libfprint-device-DEBUG: 03:38:39.698: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s (process:4386): libfprint-image_device-DEBUG: 03:38:39.699: Image device open completed 172s (process:4386): libfprint-device-DEBUG: 03:38:39.699: Device reported open completion 172s (process:4386): libfprint-device-DEBUG: 03:38:39.699: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s (process:4386): libfprint-device-DEBUG: 03:38:39.699: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s (process:4386): libfprint-device-DEBUG: 03:38:39.700: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s (process:4386): libfprint-image_device-DEBUG: 03:38:39.700: Activating image device 172s (process:4386): libfprint-image_device-DEBUG: 03:38:39.700: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 172s (process:4386): libfprint-SSM-DEBUG: 03:38:39.700: [vfs301] 1 entering state 0 172s (process:4386): libfprint-SSM-DEBUG: 03:38:39.748: [vfs301] 1 completed successfully 172s (process:4386): libfprint-image_device-DEBUG: 03:38:39.748: Image device activation completed 172s (process:4386): libfprint-image_device-DEBUG: 03:38:39.748: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 172s (process:4386): libfprint-image_device-DEBUG: 03:38:39.748: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 172s (process:4386): libfprint-SSM-DEBUG: 03:38:39.748: [vfs301] M_LOOP_NUM_STATES entering state 0 172s (process:4386): libfprint-SSM-DEBUG: 03:38:39.749: [vfs301] M_LOOP_NUM_STATES entering state 1 172s (process:4386): libfprint-device-DEBUG: 03:38:39.749: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:4386): libfprint-device-DEBUG: 03:38:39.800: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 172s (process:4386): libfprint-SSM-DEBUG: 03:38:39.949: [vfs301] M_LOOP_NUM_STATES entering state 2 172s (process:4386): libfprint-SSM-DEBUG: 03:38:39.951: [vfs301] M_LOOP_NUM_STATES entering state 1 173s (process:4386): libfprint-SSM-DEBUG: 03:38:40.151: [vfs301] M_LOOP_NUM_STATES entering state 2 173s (process:4386): libfprint-SSM-DEBUG: 03:38:40.152: [vfs301] M_LOOP_NUM_STATES entering state 3 173s (process:4386): libfprint-device-DEBUG: 03:38:40.152: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 173s (process:4386): libfprint-image_device-DEBUG: 03:38:40.152: Image device reported finger status: on 173s (process:4386): libfprint-image_device-DEBUG: 03:38:40.152: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 173s (process:4386): libfprint-SSM-DEBUG: 03:38:40.153: [vfs301] M_LOOP_NUM_STATES entering state 4 173s (process:4386): libfprint-SSM-DEBUG: 03:38:40.353: [vfs301] M_LOOP_NUM_STATES entering state 5 173s (process:4386): libfprint-SSM-DEBUG: 03:38:40.357: [vfs301] M_LOOP_NUM_STATES entering state 6 173s (process:4386): libfprint-image_device-DEBUG: 03:38:40.357: Image device captured an image 173s (process:4386): libfprint-image_device-DEBUG: 03:38:40.358: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 173s (process:4386): libfprint-device-DEBUG: 03:38:40.358: Device reported finger status change: FP_FINGER_STATUS_PRESENT 173s (process:4386): libfprint-SSM-DEBUG: 03:38:40.358: [vfs301] M_LOOP_NUM_STATES completed successfully 173s (process:4386): libfprint-device-DEBUG: 03:38:40.358: Device reported finger status change: FP_FINGER_STATUS_NONE 173s (process:4386): libfprint-image_device-DEBUG: 03:38:40.359: Image device reported finger status: off 173s (process:4386): libfprint-image_device-DEBUG: 03:38:40.360: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 173s (process:4386): libfprint-image_device-DEBUG: 03:38:40.360: Deactivating image device 173s (process:4386): libfprint-image_device-DEBUG: 03:38:40.360: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 173s (process:4386): libfprint-image_device-DEBUG: 03:38:40.360: Image device deactivation completed 173s (process:4386): libfprint-image_device-DEBUG: 03:38:40.360: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 173s (process:4386): libfprint-image-DEBUG: 03:38:40.384: Minutiae scan completed in 0.026136 secs 173s (process:4386): libfprint-device-DEBUG: 03:38:40.385: Device reported capture completion 173s (process:4386): libfprint-device-DEBUG: 03:38:40.385: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 173s (process:4386): libfprint-device-DEBUG: 03:38:40.385: Updated temperature model after 0.59 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 173s (process:4386): libfprint-image_device-DEBUG: 03:38:40.385: Image device close completed 173s (process:4386): libfprint-device-DEBUG: 03:38:40.385: Device reported close completion 173s (process:4386): libfprint-device-DEBUG: 03:38:40.385: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 173s (process:4386): libfprint-device-DEBUG: 03:38:40.385: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 173s ** (umockdev-run:4382): DEBUG: 03:38:40.484: umockdev.vala:154: Removing test bed /tmp/umockdev.6WMD22 173s (umockdev-run:4382): GLib-DEBUG: 03:38:40.492: unsetenv() is not thread-safe and should not be used after threads are created 173s Comparing PNGs /tmp/libfprint-umockdev-test-zsf_9xk8/capture.png and /usr/share/installed-tests/libfprint-2/vfs301/capture.png 173s PASS: libfprint-2/driver-vfs301.test 173s Running test: libfprint-2/driver-vfs5011.test 173s ** (umockdev-run:4395): DEBUG: 03:38:40.551: umockdev.vala:127: Created udev test bed /tmp/umockdev.KFMC22 173s ** (umockdev-run:4395): DEBUG: 03:38:40.551: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb2/2-6 173s ** (umockdev-run:4395): DEBUG: 03:38:40.552: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb2/2-6 (subsystem usb) 173s ** (umockdev-run:4395): DEBUG: 03:38:40.555: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.KFMC22/dev/bus/usb/002/017 173s ** (umockdev-run:4395): DEBUG: 03:38:40.555: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb2 173s ** (umockdev-run:4395): DEBUG: 03:38:40.556: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb2 (subsystem usb) 173s ** (umockdev-run:4395): DEBUG: 03:38:40.559: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.KFMC22/dev/bus/usb/002/001 173s ** (umockdev-run:4395): DEBUG: 03:38:40.559: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 173s ** (umockdev-run:4395): DEBUG: 03:38:40.559: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 173s (umockdev-run:4395): GLib-GIO-DEBUG: 03:38:40.561: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 173s (process:4399): libfprint-context-DEBUG: 03:38:40.661: Initializing FpContext (libfprint version 1.94.8+tod1) 173s (process:4399): libfprint-tod-DEBUG: 03:38:40.661: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 173s (process:4399): libfprint-context-DEBUG: 03:38:40.663: No driver found for USB device 1D6B:0002 173s (process:4399): libfprint-device-DEBUG: 03:38:40.663: Device reported probe completion 173s (process:4399): libfprint-device-DEBUG: 03:38:40.663: Completing action FPI_DEVICE_ACTION_PROBE in idle! 173s (process:4399): libfprint-device-DEBUG: 03:38:40.663: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.665: [vfs5011] DEV_OPEN_NUM_STATES entering state 0 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.665: [vfs5011] DEVICE OPEN entering state 0 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.665: Sending vfs5011_cmd_01 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.666: [vfs5011] DEVICE OPEN entering state 1 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.666: Receiving 64 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.666: Got 38 bytes out of 64 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.666: [vfs5011] DEVICE OPEN entering state 2 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.666: Sending vfs5011_cmd_19 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.667: [vfs5011] DEVICE OPEN entering state 3 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.667: Receiving 64 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.668: Got 64 bytes out of 64 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.668: [vfs5011] DEVICE OPEN entering state 4 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.668: Receiving 64 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.669: Got 4 bytes out of 64 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.669: [vfs5011] DEVICE OPEN entering state 5 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.669: Sending vfs5011_init_00 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.672: [vfs5011] DEVICE OPEN entering state 6 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.672: Receiving 64 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.673: Got 6 bytes out of 64 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.673: [vfs5011] DEVICE OPEN entering state 7 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.673: Sending vfs5011_init_01 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.681: [vfs5011] DEVICE OPEN entering state 8 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.681: Receiving 64 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.682: Got 7 bytes out of 64 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.682: [vfs5011] DEVICE OPEN entering state 9 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.682: Sending vfs5011_init_02 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.683: [vfs5011] DEVICE OPEN entering state 10 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.683: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.683: [vfs5011] DEVICE OPEN entering state 11 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.683: Sending vfs5011_cmd_01 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.684: [vfs5011] DEVICE OPEN entering state 12 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.684: Receiving 64 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.685: Got 38 bytes out of 64 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.685: [vfs5011] DEVICE OPEN entering state 13 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.685: Sending vfs5011_cmd_1A 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.685: [vfs5011] DEVICE OPEN entering state 14 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.685: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.686: [vfs5011] DEVICE OPEN entering state 15 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.686: Sending vfs5011_init_03 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.687: [vfs5011] DEVICE OPEN entering state 16 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.687: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.687: [vfs5011] DEVICE OPEN entering state 17 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.687: Sending vfs5011_init_04 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.688: [vfs5011] DEVICE OPEN entering state 18 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.688: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.688: [vfs5011] DEVICE OPEN entering state 19 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.688: Receiving 256 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.689: Got 256 bytes out of 256 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.689: [vfs5011] DEVICE OPEN entering state 20 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.689: Receiving 64 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.690: Got 32 bytes out of 64 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.690: [vfs5011] DEVICE OPEN entering state 21 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.690: Sending vfs5011_cmd_1A 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.690: [vfs5011] DEVICE OPEN entering state 22 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.690: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.691: [vfs5011] DEVICE OPEN entering state 23 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.691: Sending vfs5011_init_05 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.692: [vfs5011] DEVICE OPEN entering state 24 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.692: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.692: [vfs5011] DEVICE OPEN entering state 25 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.692: Sending vfs5011_cmd_01 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.693: [vfs5011] DEVICE OPEN entering state 26 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.693: Receiving 64 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.694: Got 38 bytes out of 64 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.694: [vfs5011] DEVICE OPEN entering state 27 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.694: Sending vfs5011_init_06 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.694: [vfs5011] DEVICE OPEN entering state 28 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.694: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.695: [vfs5011] DEVICE OPEN entering state 29 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.695: Receiving 17216 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.696: Got 17216 bytes out of 17216 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.696: [vfs5011] DEVICE OPEN entering state 30 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.696: Receiving 32 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.696: Got 32 bytes out of 32 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.696: [vfs5011] DEVICE OPEN entering state 31 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.696: Sending vfs5011_init_07 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.697: [vfs5011] DEVICE OPEN entering state 32 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.697: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.697: [vfs5011] DEVICE OPEN entering state 33 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.697: Receiving 45056 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.698: Got 45056 bytes out of 45056 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.698: [vfs5011] DEVICE OPEN entering state 34 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.698: Sending vfs5011_init_08 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.699: [vfs5011] DEVICE OPEN entering state 35 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.699: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.699: [vfs5011] DEVICE OPEN entering state 36 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.699: Receiving 16896 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.700: Got 16896 bytes out of 16896 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.700: [vfs5011] DEVICE OPEN entering state 37 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.700: Sending vfs5011_init_09 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.700: [vfs5011] DEVICE OPEN entering state 38 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.700: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.701: [vfs5011] DEVICE OPEN entering state 39 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.701: Receiving 4928 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.702: Got 4928 bytes out of 4928 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.702: [vfs5011] DEVICE OPEN entering state 40 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.702: Sending vfs5011_init_10 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.702: [vfs5011] DEVICE OPEN entering state 41 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.702: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.703: [vfs5011] DEVICE OPEN entering state 42 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.703: Receiving 5632 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.704: Got 5632 bytes out of 5632 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.704: [vfs5011] DEVICE OPEN entering state 43 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.704: Sending vfs5011_init_11 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.704: [vfs5011] DEVICE OPEN entering state 44 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.704: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.705: [vfs5011] DEVICE OPEN entering state 45 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.705: Receiving 5632 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.705: Got 5632 bytes out of 5632 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.705: [vfs5011] DEVICE OPEN entering state 46 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.705: Sending vfs5011_init_12 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.706: [vfs5011] DEVICE OPEN entering state 47 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.706: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.707: [vfs5011] DEVICE OPEN entering state 48 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.707: Receiving 3328 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.707: Got 3328 bytes out of 3328 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.707: [vfs5011] DEVICE OPEN entering state 49 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.707: Receiving 64 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.708: Got 32 bytes out of 64 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.708: [vfs5011] DEVICE OPEN entering state 50 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.708: Sending vfs5011_init_13 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.708: [vfs5011] DEVICE OPEN entering state 51 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.708: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.709: [vfs5011] DEVICE OPEN entering state 52 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.709: Sending vfs5011_cmd_1A 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.710: [vfs5011] DEVICE OPEN entering state 53 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.710: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.710: [vfs5011] DEVICE OPEN entering state 54 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.710: Sending vfs5011_init_03 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.711: [vfs5011] DEVICE OPEN entering state 55 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.711: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.711: [vfs5011] DEVICE OPEN entering state 56 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.711: Sending vfs5011_init_14 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.712: [vfs5011] DEVICE OPEN entering state 57 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.712: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.713: [vfs5011] DEVICE OPEN entering state 58 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.713: Receiving 4800 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.713: Got 4800 bytes out of 4800 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.713: [vfs5011] DEVICE OPEN entering state 59 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.713: Sending vfs5011_cmd_1A 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.714: [vfs5011] DEVICE OPEN entering state 60 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.714: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.714: [vfs5011] DEVICE OPEN entering state 61 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.714: Sending vfs5011_init_02 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.715: [vfs5011] DEVICE OPEN entering state 62 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.715: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.716: [vfs5011] DEVICE OPEN entering state 63 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.716: Sending vfs5011_cmd_27 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.716: [vfs5011] DEVICE OPEN entering state 64 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.716: Receiving 64 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.717: Got 22 bytes out of 64 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.717: [vfs5011] DEVICE OPEN entering state 65 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.717: Sending vfs5011_cmd_1A 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.717: [vfs5011] DEVICE OPEN entering state 66 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.717: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.718: [vfs5011] DEVICE OPEN entering state 67 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.718: Sending vfs5011_init_15 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.719: [vfs5011] DEVICE OPEN entering state 68 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.719: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.719: [vfs5011] DEVICE OPEN entering state 69 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.719: Sending vfs5011_init_16 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.720: [vfs5011] DEVICE OPEN entering state 70 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.720: Receiving 2368 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.720: Got 2368 bytes out of 2368 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.720: [vfs5011] DEVICE OPEN entering state 71 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.720: Receiving 64 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.721: Got 36 bytes out of 64 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.721: [vfs5011] DEVICE OPEN entering state 72 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.721: Receiving 4800 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.722: Got 4800 bytes out of 4800 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.722: [vfs5011] DEVICE OPEN entering state 73 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.722: Sending vfs5011_init_17 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.722: [vfs5011] DEVICE OPEN entering state 74 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.722: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.723: [vfs5011] DEVICE OPEN entering state 75 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.723: Sending vfs5011_init_18 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.723: [vfs5011] DEVICE OPEN entering state 76 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.723: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.724: [vfs5011] DEVICE OPEN completed successfully 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.724: [vfs5011] DEV_OPEN_NUM_STATES completed successfully 173s (process:4399): libfprint-image_device-DEBUG: 03:38:40.724: Image device open completed 173s (process:4399): libfprint-device-DEBUG: 03:38:40.724: Device reported open completion 173s (process:4399): libfprint-device-DEBUG: 03:38:40.724: Completing action FPI_DEVICE_ACTION_OPEN in idle! 173s (process:4399): libfprint-device-DEBUG: 03:38:40.724: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s (process:4399): libfprint-device-DEBUG: 03:38:40.724: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s (process:4399): libfprint-image_device-DEBUG: 03:38:40.724: Activating image device 173s (process:4399): libfprint-image_device-DEBUG: 03:38:40.724: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.724: device initialized 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.724: creating ssm 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.724: starting ssm 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.724: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 0 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.724: main_loop: state 0 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.724: [vfs5011] ACTIVATE REQUEST entering state 0 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.724: Sending vfs5011_cmd_04 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.725: ssm done, getting out 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.725: [vfs5011] ACTIVATE REQUEST entering state 1 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.725: Receiving 64 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.726: Got 64 bytes out of 64 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.726: [vfs5011] ACTIVATE REQUEST entering state 2 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.726: Receiving 84032 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.727: Got 176 bytes out of 84032 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.727: [vfs5011] ACTIVATE REQUEST entering state 3 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.727: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.727: [vfs5011] ACTIVATE REQUEST entering state 4 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.727: Sending vfs5011_cmd_1A 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.728: [vfs5011] ACTIVATE REQUEST entering state 5 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.728: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.729: [vfs5011] ACTIVATE REQUEST entering state 6 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.729: Sending vfs5011_prepare_00 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.729: [vfs5011] ACTIVATE REQUEST entering state 7 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.729: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.730: [vfs5011] ACTIVATE REQUEST entering state 8 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.730: Sending vfs5011_cmd_1A 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.730: [vfs5011] ACTIVATE REQUEST entering state 9 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.730: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.731: [vfs5011] ACTIVATE REQUEST entering state 10 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.731: Sending vfs5011_prepare_01 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.732: [vfs5011] ACTIVATE REQUEST entering state 11 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.732: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.732: [vfs5011] ACTIVATE REQUEST entering state 12 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.732: Sending vfs5011_prepare_02 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.733: [vfs5011] ACTIVATE REQUEST entering state 13 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.733: Receiving 2368 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.734: Got 2368 bytes out of 2368 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.734: [vfs5011] ACTIVATE REQUEST entering state 14 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.734: Receiving 64 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.734: Got 36 bytes out of 64 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.734: [vfs5011] ACTIVATE REQUEST entering state 15 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.734: Receiving 4800 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.735: Got 4800 bytes out of 4800 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.735: [vfs5011] ACTIVATE REQUEST entering state 16 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.735: Sending vfs5011_prepare_03 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.735: [vfs5011] ACTIVATE REQUEST entering state 17 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.735: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.736: [vfs5011] ACTIVATE REQUEST entering state 18 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.736: Sending vfs5011_prepare_04 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.737: [vfs5011] ACTIVATE REQUEST entering state 19 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.737: Receiving 2368 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.737: [vfs5011] ACTIVATE REQUEST completed successfully 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.737: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 1 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.737: main_loop: state 1 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.737: capture_init 173s (process:4399): libfprint-image_device-DEBUG: 03:38:40.737: Image device activation completed 173s (process:4399): libfprint-image_device-DEBUG: 03:38:40.737: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 173s (process:4399): libfprint-image_device-DEBUG: 03:38:40.737: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 173s (process:4399): libfprint-device-DEBUG: 03:38:40.737: Device reported finger status change: FP_FINGER_STATUS_NEEDED 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.737: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.737: main_loop: state 2 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.737: capture_chunk_async: capture 256 lines, already have 0 173s (process:4399): libfprint-device-DEBUG: 03:38:40.738: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 173s (process:4399): libfprint-image_device-DEBUG: 03:38:40.738: Image device reported finger status: on 173s (process:4399): libfprint-image_device-DEBUG: 03:38:40.738: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.738: process_chunk: got 61440 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.738: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.738: main_loop: state 2 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.738: capture_chunk_async: capture 256 lines, already have 6 173s (process:4399): libfprint-image_device-DEBUG: 03:38:40.739: Image device reported finger status: on 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.739: process_chunk: got 61440 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.739: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.739: main_loop: state 2 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.739: capture_chunk_async: capture 256 lines, already have 25 173s (process:4399): libfprint-image_device-DEBUG: 03:38:40.740: Image device reported finger status: on 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.740: process_chunk: got 61440 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.740: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.740: main_loop: state 2 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.740: capture_chunk_async: capture 256 lines, already have 54 173s (process:4399): libfprint-image_device-DEBUG: 03:38:40.741: Image device reported finger status: on 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.741: process_chunk: got 61440 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.741: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.741: main_loop: state 2 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.741: capture_chunk_async: capture 256 lines, already have 89 173s (process:4399): libfprint-image_device-DEBUG: 03:38:40.742: Image device reported finger status: on 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.742: process_chunk: got 61440 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.742: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.742: main_loop: state 2 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.742: capture_chunk_async: capture 256 lines, already have 117 173s (process:4399): libfprint-image_device-DEBUG: 03:38:40.743: Image device reported finger status: on 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.743: process_chunk: got 61440 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.743: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.743: main_loop: state 2 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.743: capture_chunk_async: capture 256 lines, already have 144 173s (process:4399): libfprint-image_device-DEBUG: 03:38:40.744: Image device reported finger status: on 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.744: process_chunk: got 61440 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.744: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.744: main_loop: state 2 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.744: capture_chunk_async: capture 256 lines, already have 180 173s (process:4399): libfprint-image_device-DEBUG: 03:38:40.744: Image device reported finger status: on 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.744: process_chunk: got 61440 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.744: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.744: main_loop: state 2 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.744: capture_chunk_async: capture 256 lines, already have 273 173s (process:4399): libfprint-image_device-DEBUG: 03:38:40.745: Image device reported finger status: on 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.745: process_chunk: got 61440 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.745: process_chunk: got 50 empty lines, finishing 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.745: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 3 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.745: main_loop: state 3 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.746: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 4 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.746: main_loop: state 4 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.746: [vfs5011] PREPARE CAPTURE entering state 0 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.746: Sending vfs5011_cmd_04 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.747: [vfs5011] PREPARE CAPTURE entering state 1 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.747: Receiving 64 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.747: Got 64 bytes out of 64 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.747: [vfs5011] PREPARE CAPTURE entering state 2 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.747: Receiving 84032 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.748: Got 176 bytes out of 84032 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.748: [vfs5011] PREPARE CAPTURE entering state 3 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.748: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.749: [vfs5011] PREPARE CAPTURE entering state 4 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.749: Sending vfs5011_cmd_1A 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.749: [vfs5011] PREPARE CAPTURE entering state 5 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.749: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.750: [vfs5011] PREPARE CAPTURE entering state 6 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.750: Sending vfs5011_prepare_00 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.751: [vfs5011] PREPARE CAPTURE entering state 7 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.751: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.751: [vfs5011] PREPARE CAPTURE entering state 8 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.751: Sending vfs5011_cmd_1A 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.752: [vfs5011] PREPARE CAPTURE entering state 9 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.752: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.752: [vfs5011] PREPARE CAPTURE entering state 10 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.752: Sending vfs5011_prepare_01 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.753: [vfs5011] PREPARE CAPTURE entering state 11 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.753: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.754: [vfs5011] PREPARE CAPTURE entering state 12 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.754: Sending vfs5011_prepare_02 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.754: [vfs5011] PREPARE CAPTURE entering state 13 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.754: Receiving 2368 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.755: Got 2368 bytes out of 2368 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.755: [vfs5011] PREPARE CAPTURE entering state 14 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.755: Receiving 64 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.755: Got 36 bytes out of 64 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.755: [vfs5011] PREPARE CAPTURE entering state 15 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.755: Receiving 4800 bytes 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.756: Got 4800 bytes out of 4800 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.756: [vfs5011] PREPARE CAPTURE entering state 16 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.756: Sending vfs5011_prepare_03 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.757: [vfs5011] PREPARE CAPTURE entering state 17 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.757: Receiving 64 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.757: [vfs5011] PREPARE CAPTURE entering state 18 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.757: Sending vfs5011_prepare_04 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.758: [vfs5011] PREPARE CAPTURE entering state 19 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.758: Receiving 2368 bytes 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.759: [vfs5011] PREPARE CAPTURE completed successfully 173s (process:4399): libfprint-SSM-DEBUG: 03:38:40.759: [vfs5011] DEV_ACTIVATE_NUM_STATES completed successfully 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.759: finishing 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 1739677120759115 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 1 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 5 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 4 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 4 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 3 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 3 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 5 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 4 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 27 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 27 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 27 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 27 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 28 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 5 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 28 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 29 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 29 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 29 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 29 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 28 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 28 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 29 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 28 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 30 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 29 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 30 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 5 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 5 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 30 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 30 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 30 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 30 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 30 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 4 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 4 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 29 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 30 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 29 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 9 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 30 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 30 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 30 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 30 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 30 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 9 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 9 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 9 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 9 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 9 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 9 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 9 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 29 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 29 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 11 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 9 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 9 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 9 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 9 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 9 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 30 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 9 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 27 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 26 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 5 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 4 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.759: 2 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: offsets_filtered: 1739677120760076 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 5 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 5 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 5 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 5 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 5 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 27 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 27 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 27 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 27 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 27 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 27 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 27 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 28 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 28 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 28 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 28 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 28 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 28 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 28 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 28 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 28 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 29 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 29 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 29 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 29 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 29 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 29 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 28 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 28 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 28 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 6 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 9 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 9 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 9 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 9 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 9 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 9 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 9 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 9 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 9 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 9 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 9 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 9 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 8 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 7 173s (process:4399): libfprint-assembling-DEBUG: 03:38:40.760: 2 173s (process:4399): libfprint-vfs5011-DEBUG: 03:38:40.761: Image captured, committing 173s (process:4399): libfprint-image_device-DEBUG: 03:38:40.761: Image device captured an image 173s (process:4399): libfprint-image_device-DEBUG: 03:38:40.761: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 173s (process:4399): libfprint-device-DEBUG: 03:38:40.761: Device reported finger status change: FP_FINGER_STATUS_PRESENT 173s (process:4399): libfprint-device-DEBUG: 03:38:40.761: Device reported finger status change: FP_FINGER_STATUS_NONE 173s (process:4399): libfprint-image_device-DEBUG: 03:38:40.761: Image device reported finger status: off 173s (process:4399): libfprint-image_device-DEBUG: 03:38:40.761: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 173s (process:4399): libfprint-image_device-DEBUG: 03:38:40.761: Deactivating image device 173s (process:4399): libfprint-image_device-DEBUG: 03:38:40.761: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 173s (process:4399): libfprint-image_device-DEBUG: 03:38:40.761: Image device deactivation completed 173s (process:4399): libfprint-image_device-DEBUG: 03:38:40.761: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 173s (process:4399): libfprint-image-DEBUG: 03:38:40.787: Minutiae scan completed in 0.025586 secs 173s (process:4399): libfprint-device-DEBUG: 03:38:40.787: Device reported capture completion 173s (process:4399): libfprint-device-DEBUG: 03:38:40.787: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 173s (process:4399): libfprint-device-DEBUG: 03:38:40.787: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 173s (process:4399): libfprint-image_device-DEBUG: 03:38:40.788: Image device close completed 173s (process:4399): libfprint-device-DEBUG: 03:38:40.788: Device reported close completion 173s (process:4399): libfprint-device-DEBUG: 03:38:40.788: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 173s (process:4399): libfprint-device-DEBUG: 03:38:40.788: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 173s ** (umockdev-run:4395): DEBUG: 03:38:40.899: umockdev.vala:154: Removing test bed /tmp/umockdev.KFMC22 173s (umockdev-run:4395): GLib-DEBUG: 03:38:40.905: unsetenv() is not thread-safe and should not be used after threads are created 173s Comparing PNGs /tmp/libfprint-umockdev-test-qpngkbka/capture.png and /usr/share/installed-tests/libfprint-2/vfs5011/capture.png 173s PASS: libfprint-2/driver-vfs5011.test 173s Running test: libfprint-2/fpi-assembling.test 173s TAP version 14 173s # random seed: R02S524565dedf06abdab3413eac70524995 173s 1..1 173s # Start of assembling tests 174s # libfprint-assembling-DEBUG: calc delta completed in 0.081587 secs 174s # libfprint-assembling-DEBUG: calc delta completed in 0.081160 secs 174s # libfprint-assembling-DEBUG: errors: 0 rev: 130848 174s # libfprint-assembling-DEBUG: calc delta completed in 0.080496 secs 174s # libfprint-assembling-DEBUG: height is 310 174s ok 1 /assembling/frames 174s # End of assembling tests 174s PASS: libfprint-2/fpi-assembling.test 174s Running test: libfprint-2/virtual-device.test 174s Executing: libfprint-2/virtual-device.test 174s (process:4408): libfprint-context-DEBUG: 03:38:41.291: Initializing FpContext (libfprint version 1.94.8+tod1) 174s (process:4408): libfprint-tod-DEBUG: 03:38:41.291: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 174s (process:4408): libfprint-context-DEBUG: 03:38:41.295: No driver found for USB device 1D6B:0003 174s (process:4408): libfprint-context-DEBUG: 03:38:41.295: No driver found for USB device 0627:0001 174s (process:4408): libfprint-context-DEBUG: 03:38:41.295: No driver found for USB device 0627:0001 174s (process:4408): libfprint-context-DEBUG: 03:38:41.295: No driver found for USB device 1D6B:0002 174s (process:4408): libfprint-context-DEBUG: 03:38:41.295: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-38b_y_8y/virtual-device.socket 174s (process:4408): libfprint-context-DEBUG: 03:38:41.295: created 174s (process:4408): libfprint-device-DEBUG: 03:38:41.296: Device reported probe completion 174s (process:4408): libfprint-device-DEBUG: 03:38:41.296: Completing action FPI_DEVICE_ACTION_PROBE in idle! 174s (process:4408): libfprint-device-DEBUG: 03:38:41.296: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 174s test_capture_unsupported (__main__.VirtualDevice.test_capture_unsupported) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.297: 121105034: ../libfprint/drivers/virtual-device.c:387 174s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:41.297: 121105106: ../libfprint/drivers/virtual-device-listener.c:153 174s (process:4408): libfprint-device-DEBUG: 03:38:41.297: Device reported open completion 174s (process:4408): libfprint-device-DEBUG: 03:38:41.297: Completing action FPI_DEVICE_ACTION_OPEN in idle! 174s (process:4408): libfprint-device-DEBUG: 03:38:41.297: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 174s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:41.298: Got a new connection! 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.298: Got instructions of length 16 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.298: Received command SET_KEEP_ALIVE 0 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.298: Keep alive toggled: 0 174s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:41.298: Got a new connection! 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.298: Got instructions of length 19 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.298: Received command SET_ENROLL_STAGES 5 174s (process:4408): libfprint-device-DEBUG: 03:38:41.298: Device reported close completion 174s (process:4408): libfprint-device-DEBUG: 03:38:41.298: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 174s (process:4408): libfprint-device-DEBUG: 03:38:41.298: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 174s ok 174s test_change_enroll_stages (__main__.VirtualDevice.test_change_enroll_stages) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.298: 121106357: ../libfprint/drivers/virtual-device.c:387 174s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:41.298: 121106369: ../libfprint/drivers/virtual-device-listener.c:153 174s (process:4408): libfprint-device-DEBUG: 03:38:41.298: Device reported open completion 174s (process:4408): libfprint-device-DEBUG: 03:38:41.298: Completing action FPI_DEVICE_ACTION_OPEN in idle! 174s (process:4408): libfprint-device-DEBUG: 03:38:41.298: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 174s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:41.298: Got a new connection! 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.299: Got instructions of length 20 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.299: Received command SET_ENROLL_STAGES 20 174s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:41.299: Got a new connection! 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.299: Got instructions of length 19 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.299: Received command SET_ENROLL_STAGES 1 174s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:41.299: Got a new connection! 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.299: Got instructions of length 19 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.299: Received command SET_ENROLL_STAGES 0 174s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:41.302: Got a new connection! 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.302: Got instructions of length 16 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.302: Received command SET_KEEP_ALIVE 0 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.302: Keep alive toggled: 0 174s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:41.302: Got a new connection! 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.302: Got instructions of length 19 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.302: Received command SET_ENROLL_STAGES 5 174s (process:4408): libfprint-device-DEBUG: 03:38:41.302: Device reported close completion 174s (process:4408): libfprint-device-DEBUG: 03:38:41.302: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 174s (process:4408): libfprint-device-DEBUG: 03:38:41.302: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 174s ok 174s test_change_scan_type (__main__.VirtualDevice.test_change_scan_type) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.302: 121110317: ../libfprint/drivers/virtual-device.c:387 174s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:41.302: 121110328: ../libfprint/drivers/virtual-device-listener.c:153 174s (process:4408): libfprint-device-DEBUG: 03:38:41.302: Device reported open completion 174s (process:4408): libfprint-device-DEBUG: 03:38:41.302: Completing action FPI_DEVICE_ACTION_OPEN in idle! 174s (process:4408): libfprint-device-DEBUG: 03:38:41.302: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 174s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:41.303: Got a new connection! 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.303: Got instructions of length 19 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.303: Received command SET_SCAN_TYPE press 174s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:41.303: Got a new connection! 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.303: Got instructions of length 19 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.303: Received command SET_SCAN_TYPE swipe 174s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:41.303: Got a new connection! 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.303: Got instructions of length 25 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.303: Received command SET_SCAN_TYPE eye-contact 174s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:41.303: Got a new connection! 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.303: Got instructions of length 16 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.303: Received command SET_KEEP_ALIVE 0 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.303: Keep alive toggled: 0 174s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:41.304: Got a new connection! 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.304: Got instructions of length 19 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.304: Received command SET_ENROLL_STAGES 5 174s (process:4408): libfprint-device-DEBUG: 03:38:41.304: Device reported close completion 174s (process:4408): libfprint-device-DEBUG: 03:38:41.304: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 174s (process:4408): libfprint-device-DEBUG: 03:38:41.304: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 174s ok 174s test_close_error (__main__.VirtualDevice.test_close_error) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.304: 121111910: ../libfprint/drivers/virtual-device.c:387 174s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:41.304: 121111921: ../libfprint/drivers/virtual-device-listener.c:153 174s (process:4408): libfprint-device-DEBUG: 03:38:41.304: Device reported open completion 174s (process:4408): libfprint-device-DEBUG: 03:38:41.304: Completing action FPI_DEVICE_ACTION_OPEN in idle! 174s (process:4408): libfprint-device-DEBUG: 03:38:41.304: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 174s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:41.304: Got a new connection! 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.304: Got instructions of length 9 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.304: Received command SLEEP 100 174s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:41.304: Got a new connection! 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.304: Got instructions of length 7 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.304: Received command ERROR 4 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.305: Processing command SLEEP 100 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.305: Sleeping 100ms 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.405: Sleeping completed 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.405: Processing command ERROR 4 174s (process:4408): libfprint-device-DEBUG: 03:38:41.405: Device reported close completion 174s (process:4408): libfprint-device-DEBUG: 03:38:41.405: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 174s (process:4408): libfprint-device-DEBUG: 03:38:41.405: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 174s ok 174s test_close_while_opening (__main__.VirtualDevice.test_close_while_opening) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.405: 121213479: ../libfprint/drivers/virtual-device.c:387 174s (process:4408): libfprint-device-DEBUG: 03:38:41.405: Device reported open completion 174s (process:4408): libfprint-device-DEBUG: 03:38:41.405: Completing action FPI_DEVICE_ACTION_OPEN in idle! 174s (process:4408): libfprint-device-DEBUG: 03:38:41.405: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 174s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:41.406: Got a new connection! 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.406: Got instructions of length 16 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.406: Received command SET_KEEP_ALIVE 1 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.406: Keep alive toggled: 1 174s (process:4408): libfprint-device-DEBUG: 03:38:41.406: Device reported close completion 174s (process:4408): libfprint-device-DEBUG: 03:38:41.406: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 174s (process:4408): libfprint-device-DEBUG: 03:38:41.406: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 174s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:41.406: Got a new connection! 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.406: Got instructions of length 9 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.406: Received command SLEEP 500 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.406: 121214044: ../libfprint/drivers/virtual-device.c:387 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.406: Processing command SLEEP 500 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.406: Sleeping 500ms 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.907: Sleeping completed 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.907: 121714679: ../libfprint/drivers/virtual-device.c:387 174s (process:4408): libfprint-device-DEBUG: 03:38:41.907: Device reported open completion 174s (process:4408): libfprint-device-DEBUG: 03:38:41.907: Completing action FPI_DEVICE_ACTION_OPEN in idle! 174s (process:4408): libfprint-device-DEBUG: 03:38:41.907: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 174s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:41.907: Got a new connection! 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.907: Got instructions of length 16 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.907: Received command SET_KEEP_ALIVE 0 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.907: Keep alive toggled: 0 174s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:41.907: Got a new connection! 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.907: Got instructions of length 19 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.907: Received command SET_ENROLL_STAGES 5 174s (process:4408): libfprint-device-DEBUG: 03:38:41.907: Device reported close completion 174s (process:4408): libfprint-device-DEBUG: 03:38:41.907: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 174s (process:4408): libfprint-device-DEBUG: 03:38:41.907: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 174s ok 174s test_delayed_open (__main__.VirtualDevice.test_delayed_open) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.907: 121715509: ../libfprint/drivers/virtual-device.c:387 174s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:41.907: 121715519: ../libfprint/drivers/virtual-device-listener.c:153 174s (process:4408): libfprint-device-DEBUG: 03:38:41.907: Device reported open completion 174s (process:4408): libfprint-device-DEBUG: 03:38:41.908: Completing action FPI_DEVICE_ACTION_OPEN in idle! 174s (process:4408): libfprint-device-DEBUG: 03:38:41.908: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 174s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:41.908: Got a new connection! 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.908: Got instructions of length 16 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.908: Received command IGNORED_COMMAND 174s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:41.908: Got a new connection! 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.908: Got instructions of length 9 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.908: Received command SLEEP 500 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.908: Processing command IGNORED_COMMAND 174s (process:4408): libfprint-device-DEBUG: 03:38:41.908: Device reported close completion 174s (process:4408): libfprint-device-DEBUG: 03:38:41.908: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 174s (process:4408): libfprint-device-DEBUG: 03:38:41.908: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.908: 121716260: ../libfprint/drivers/virtual-device.c:387 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.908: Processing command SLEEP 500 174s (process:4408): libfprint-virtual_device-DEBUG: 03:38:41.908: Sleeping 500ms 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.409: Sleeping completed 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.409: 122216886: ../libfprint/drivers/virtual-device.c:387 175s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:42.409: 122216904: ../libfprint/drivers/virtual-device-listener.c:153 175s (process:4408): libfprint-device-DEBUG: 03:38:42.409: Device reported open completion 175s (process:4408): libfprint-device-DEBUG: 03:38:42.409: Completing action FPI_DEVICE_ACTION_OPEN in idle! 175s (process:4408): libfprint-device-DEBUG: 03:38:42.409: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 175s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:42.409: Got a new connection! 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.409: Got instructions of length 16 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.409: Received command SET_KEEP_ALIVE 0 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.409: Keep alive toggled: 0 175s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:42.409: Got a new connection! 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.409: Got instructions of length 19 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.409: Received command SET_ENROLL_STAGES 5 175s (process:4408): libfprint-device-DEBUG: 03:38:42.410: Device reported close completion 175s (process:4408): libfprint-device-DEBUG: 03:38:42.410: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 175s (process:4408): libfprint-device-DEBUG: 03:38:42.410: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 175s ok 175s test_delayed_open_with_keep_alive (__main__.VirtualDevice.test_delayed_open_with_keep_alive) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.410: 122217797: ../libfprint/drivers/virtual-device.c:387 175s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:42.410: 122217809: ../libfprint/drivers/virtual-device-listener.c:153 175s (process:4408): libfprint-device-DEBUG: 03:38:42.410: Device reported open completion 175s (process:4408): libfprint-device-DEBUG: 03:38:42.410: Completing action FPI_DEVICE_ACTION_OPEN in idle! 175s (process:4408): libfprint-device-DEBUG: 03:38:42.410: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 175s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:42.410: Got a new connection! 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.410: Got instructions of length 16 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.410: Received command SET_KEEP_ALIVE 1 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.410: Keep alive toggled: 1 175s (process:4408): libfprint-device-DEBUG: 03:38:42.410: Device reported close completion 175s (process:4408): libfprint-device-DEBUG: 03:38:42.410: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 175s (process:4408): libfprint-device-DEBUG: 03:38:42.410: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 175s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:42.410: Got a new connection! 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.410: Got instructions of length 9 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.410: Received command SLEEP 500 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.410: 122218323: ../libfprint/drivers/virtual-device.c:387 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.410: Processing command SLEEP 500 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.410: Sleeping 500ms 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.911: Sleeping completed 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.911: 122718955: ../libfprint/drivers/virtual-device.c:387 175s (process:4408): libfprint-device-DEBUG: 03:38:42.911: Device reported open completion 175s (process:4408): libfprint-device-DEBUG: 03:38:42.911: Completing action FPI_DEVICE_ACTION_OPEN in idle! 175s (process:4408): libfprint-device-DEBUG: 03:38:42.911: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 175s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:42.911: Got a new connection! 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.911: Got instructions of length 16 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.911: Received command SET_KEEP_ALIVE 0 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.911: Keep alive toggled: 0 175s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:42.911: Got a new connection! 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.911: Got instructions of length 19 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.911: Received command SET_ENROLL_STAGES 5 175s (process:4408): libfprint-device-DEBUG: 03:38:42.911: Device reported close completion 175s (process:4408): libfprint-device-DEBUG: 03:38:42.912: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 175s (process:4408): libfprint-device-DEBUG: 03:38:42.912: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 175s ok 175s test_device_features (__main__.VirtualDevice.test_device_features) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.912: 122719731: ../libfprint/drivers/virtual-device.c:387 175s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:42.912: 122719740: ../libfprint/drivers/virtual-device-listener.c:153 175s /usr/libexec/installed-tests/libfprint-2/virtual-device.py:463: DeprecationWarning: FPrint.Device.supports_identify is deprecated 175s self.assertFalse(self.dev.supports_identify()) 175s /usr/libexec/installed-tests/libfprint-2/virtual-device.py:464: DeprecationWarning: FPrint.Device.supports_capture is deprecated 175s self.assertFalse(self.dev.supports_capture()) 175s /usr/libexec/installed-tests/libfprint-2/virtual-device.py:465: DeprecationWarning: FPrint.Device.has_storage is deprecated 175s self.assertFalse(self.dev.has_storage()) 175s (process:4408): libfprint-device-DEBUG: 03:38:42.912: Device reported open completion 175s (process:4408): libfprint-device-DEBUG: 03:38:42.912: Completing action FPI_DEVICE_ACTION_OPEN in idle! 175s (process:4408): libfprint-device-DEBUG: 03:38:42.912: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 175s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:42.912: Got a new connection! 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.912: Got instructions of length 16 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.912: Received command SET_KEEP_ALIVE 0 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.912: Keep alive toggled: 0 175s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:42.913: Got a new connection! 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.913: Got instructions of length 19 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.913: Received command SET_ENROLL_STAGES 5 175s (process:4408): libfprint-device-DEBUG: 03:38:42.913: Device reported close completion 175s (process:4408): libfprint-device-DEBUG: 03:38:42.913: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 175s (process:4408): libfprint-device-DEBUG: 03:38:42.913: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 175s ok 175s test_device_properties (__main__.VirtualDevice.test_device_properties) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.913: 122720865: ../libfprint/drivers/virtual-device.c:387 175s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:42.913: 122720874: ../libfprint/drivers/virtual-device-listener.c:153 175s (process:4408): libfprint-device-DEBUG: 03:38:42.913: Device reported open completion 175s (process:4408): libfprint-device-DEBUG: 03:38:42.913: Completing action FPI_DEVICE_ACTION_OPEN in idle! 175s (process:4408): libfprint-device-DEBUG: 03:38:42.913: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 175s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:42.913: Got a new connection! 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.913: Got instructions of length 16 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.913: Received command SET_KEEP_ALIVE 0 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.913: Keep alive toggled: 0 175s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:42.913: Got a new connection! 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.913: Got instructions of length 19 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.913: Received command SET_ENROLL_STAGES 5 175s (process:4408): libfprint-device-DEBUG: 03:38:42.913: Device reported close completion 175s (process:4408): libfprint-device-DEBUG: 03:38:42.913: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 175s (process:4408): libfprint-device-DEBUG: 03:38:42.913: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 175s ok 175s test_device_sleep (__main__.VirtualDevice.test_device_sleep) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.914: 122721669: ../libfprint/drivers/virtual-device.c:387 175s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:42.914: 122721677: ../libfprint/drivers/virtual-device-listener.c:153 175s (process:4408): libfprint-device-DEBUG: 03:38:42.914: Device reported open completion 175s (process:4408): libfprint-device-DEBUG: 03:38:42.914: Completing action FPI_DEVICE_ACTION_OPEN in idle! 175s (process:4408): libfprint-device-DEBUG: 03:38:42.914: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 175s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:42.914: Got a new connection! 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.914: Got instructions of length 10 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.914: Received command SLEEP 1500 175s (process:4408): libfprint-device-DEBUG: 03:38:42.914: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.914: Processing command SLEEP 1500 175s (process:4408): libfprint-virtual_device-DEBUG: 03:38:42.914: Sleeping 1500ms 176s (process:4408): libfprint-device-DEBUG: 03:38:43.212: Updated temperature model after 0.30 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 176s (process:4408): libfprint-device-DEBUG: 03:38:43.214: Idle cancelling on ongoing operation! 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.214: Got cancellation! 176s (process:4408): libfprint-device-DEBUG: 03:38:43.215: Device reported finger status change: FP_FINGER_STATUS_NEEDED 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.215: Virtual device scan failed with error: Operation was cancelled 176s (process:4408): libfprint-device-DEBUG: 03:38:43.215: Device reported verify completion 176s (process:4408): libfprint-device-DEBUG: 03:38:43.215: Device reported finger status change: FP_FINGER_STATUS_NONE 176s (process:4408): libfprint-device-DEBUG: 03:38:43.215: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 176s (process:4408): libfprint-device-DEBUG: 03:38:43.215: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 176s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:43.415: Got a new connection! 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.415: Got instructions of length 16 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.415: Received command SET_KEEP_ALIVE 0 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.415: Keep alive toggled: 0 176s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:43.415: Got a new connection! 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.415: Got instructions of length 19 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.415: Received command SET_ENROLL_STAGES 5 176s (process:4408): libfprint-device-DEBUG: 03:38:43.415: Device reported close completion 176s (process:4408): libfprint-device-DEBUG: 03:38:43.415: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 176s (process:4408): libfprint-device-DEBUG: 03:38:43.415: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 176s ok 176s test_device_sleep_before_completing_verify (__main__.VirtualDevice.test_device_sleep_before_completing_verify) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.415: 123223527: ../libfprint/drivers/virtual-device.c:387 176s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:43.415: 123223550: ../libfprint/drivers/virtual-device-listener.c:153 176s (process:4408): libfprint-device-DEBUG: 03:38:43.416: Device reported open completion 176s (process:4408): libfprint-device-DEBUG: 03:38:43.416: Completing action FPI_DEVICE_ACTION_OPEN in idle! 176s (process:4408): libfprint-device-DEBUG: 03:38:43.416: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 176s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:43.416: Got a new connection! 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.416: Got instructions of length 14 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.416: Received command SCAN foo-print 176s (process:4408): libfprint-device-DEBUG: 03:38:43.416: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.416: Processing command SCAN foo-print 176s (process:4408): libfprint-device-DEBUG: 03:38:43.416: Device reported finger status change: FP_FINGER_STATUS_NEEDED 176s (process:4408): libfprint-device-DEBUG: 03:38:43.416: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 176s (process:4408): libfprint-device-DEBUG: 03:38:43.416: Device reported finger status change: FP_FINGER_STATUS_NEEDED 176s (process:4408): libfprint-device-DEBUG: 03:38:43.416: Device reported enroll progress, reported 1 of 5 have been completed 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.416: Sleeping completed 176s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:43.417: Got a new connection! 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.417: Got instructions of length 14 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.417: Received command SCAN foo-print 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.417: Processing command SCAN foo-print 176s (process:4408): libfprint-device-DEBUG: 03:38:43.417: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 176s (process:4408): libfprint-device-DEBUG: 03:38:43.417: Device reported finger status change: FP_FINGER_STATUS_NEEDED 176s (process:4408): libfprint-device-DEBUG: 03:38:43.417: Device reported enroll progress, reported 2 of 5 have been completed 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.417: Sleeping completed 176s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:43.417: Got a new connection! 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.417: Got instructions of length 14 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.417: Received command SCAN foo-print 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.417: Processing command SCAN foo-print 176s (process:4408): libfprint-device-DEBUG: 03:38:43.417: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 176s (process:4408): libfprint-device-DEBUG: 03:38:43.417: Device reported finger status change: FP_FINGER_STATUS_NEEDED 176s (process:4408): libfprint-device-DEBUG: 03:38:43.417: Device reported enroll progress, reported 3 of 5 have been completed 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.417: Sleeping completed 176s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:43.417: Got a new connection! 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.417: Got instructions of length 14 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.417: Received command SCAN foo-print 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.417: Processing command SCAN foo-print 176s (process:4408): libfprint-device-DEBUG: 03:38:43.417: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 176s (process:4408): libfprint-device-DEBUG: 03:38:43.417: Device reported finger status change: FP_FINGER_STATUS_NEEDED 176s (process:4408): libfprint-device-DEBUG: 03:38:43.417: Device reported enroll progress, reported 4 of 5 have been completed 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.417: Sleeping completed 176s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:43.418: Got a new connection! 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.418: Got instructions of length 14 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.418: Received command SCAN foo-print 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.418: Processing command SCAN foo-print 176s (process:4408): libfprint-device-DEBUG: 03:38:43.418: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 176s (process:4408): libfprint-device-DEBUG: 03:38:43.418: Device reported finger status change: FP_FINGER_STATUS_NEEDED 176s (process:4408): libfprint-device-DEBUG: 03:38:43.418: Device reported enroll progress, reported 5 of 5 have been completed 176s (process:4408): libfprint-device-DEBUG: 03:38:43.418: Device reported enroll completion 176s (process:4408): libfprint-device-DEBUG: 03:38:43.418: Device reported finger status change: FP_FINGER_STATUS_NONE 176s (process:4408): libfprint-device-DEBUG: 03:38:43.418: Print for finger FP_FINGER_LEFT_RING enrolled 176s (process:4408): libfprint-device-DEBUG: 03:38:43.418: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 176s (process:4408): libfprint-device-DEBUG: 03:38:43.418: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 176s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:43.418: Got a new connection! 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.418: Got instructions of length 9 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.418: Received command SLEEP 100 176s (process:4408): libfprint-device-DEBUG: 03:38:43.418: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.418: Processing command SLEEP 100 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.418: Sleeping 100ms 176s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:43.419: Got a new connection! 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.419: Got instructions of length 14 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.419: Received command SCAN bar-print 176s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:43.419: Got a new connection! 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.419: Got instructions of length 9 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.419: Received command SLEEP 800 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.519: Sleeping completed 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.519: Processing command SCAN bar-print 176s (process:4408): libfprint-device-DEBUG: 03:38:43.519: Device reported finger status change: FP_FINGER_STATUS_NEEDED 176s (process:4408): libfprint-device-DEBUG: 03:38:43.519: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.519: Virtual device scanned print bar-print 176s (process:4408): libfprint-device-DEBUG: 03:38:43.519: Device reported verify result 176s (process:4408): libfprint-device-DEBUG: 03:38:43.519: Device reported finger status change: FP_FINGER_STATUS_NEEDED 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.519: Processing command SLEEP 800 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.519: Sleeping 800ms 176s (process:4408): libfprint-virtual_device-DEBUG: 03:38:43.519: Sleeping now, command queued for later: SCAN bar-print 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:44.320: Sleeping completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:44.320: Processing command SCAN bar-print 178s (process:4408): libfprint-device-DEBUG: 03:38:44.320: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:44.320: Virtual device scanned print bar-print 178s (process:4408): libfprint-device-DEBUG: 03:38:44.320: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:4408): libfprint-device-DEBUG: 03:38:44.320: Device reported verify completion 178s (process:4408): libfprint-device-DEBUG: 03:38:44.320: Device reported finger status change: FP_FINGER_STATUS_NONE 178s (process:4408): libfprint-device-DEBUG: 03:38:44.320: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 178s (process:4408): libfprint-device-DEBUG: 03:38:44.320: Updated temperature model after 0.90 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:44.320: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:44.320: Got instructions of length 16 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:44.320: Received command SET_KEEP_ALIVE 0 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:44.320: Keep alive toggled: 0 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:44.320: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:44.321: Got instructions of length 19 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:44.321: Received command SET_ENROLL_STAGES 5 178s (process:4408): libfprint-device-DEBUG: 03:38:44.321: Device reported close completion 178s (process:4408): libfprint-device-DEBUG: 03:38:44.321: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 178s (process:4408): libfprint-device-DEBUG: 03:38:44.321: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s Enroll done 178s ok 178s test_device_sleep_on_cancellation (__main__.VirtualDevice.test_device_sleep_on_cancellation) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:44.321: 124128987: ../libfprint/drivers/virtual-device.c:387 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:44.321: 124129009: ../libfprint/drivers/virtual-device-listener.c:153 178s (process:4408): libfprint-device-DEBUG: 03:38:44.321: Device reported open completion 178s (process:4408): libfprint-device-DEBUG: 03:38:44.321: Completing action FPI_DEVICE_ACTION_OPEN in idle! 178s (process:4408): libfprint-device-DEBUG: 03:38:44.321: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:44.321: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:44.321: Got instructions of length 26 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:44.321: Received command SET_CANCELLATION_ENABLED 0 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:44.321: Cancellation support toggled: 0 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:44.321: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:44.321: Got instructions of length 10 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:44.321: Received command SLEEP 1500 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:44.322: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:44.322: Got instructions of length 14 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:44.322: Received command SCAN foo-print 178s (process:4408): libfprint-device-DEBUG: 03:38:44.322: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:44.322: Processing command SLEEP 1500 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:44.322: Sleeping 1500ms 178s (process:4408): libfprint-device-DEBUG: 03:38:44.622: Idle cancelling on ongoing operation! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.823: Sleeping completed 178s (process:4408): libfprint-device-DEBUG: 03:38:45.823: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.823: Virtual device scan failed with error: Operation was cancelled 178s (process:4408): libfprint-device-DEBUG: 03:38:45.823: Device reported verify completion 178s (process:4408): libfprint-device-DEBUG: 03:38:45.823: Device reported finger status change: FP_FINGER_STATUS_NONE 178s (process:4408): libfprint-device-DEBUG: 03:38:45.823: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 178s (process:4408): libfprint-device-DEBUG: 03:38:45.823: Updated temperature model after 1.50 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.823: Processing command SCAN foo-print 178s (process:4408): libfprint-device-DEBUG: 03:38:45.823: Device reported close completion 178s (process:4408): libfprint-device-DEBUG: 03:38:45.823: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 178s (process:4408): libfprint-device-DEBUG: 03:38:45.823: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s ok 178s test_enroll (__main__.VirtualDevice.test_enroll) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.824: 125631652: ../libfprint/drivers/virtual-device.c:387 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.824: 125631675: ../libfprint/drivers/virtual-device-listener.c:153 178s (process:4408): libfprint-device-DEBUG: 03:38:45.824: Device reported open completion 178s (process:4408): libfprint-device-DEBUG: 03:38:45.824: Completing action FPI_DEVICE_ACTION_OPEN in idle! 178s (process:4408): libfprint-device-DEBUG: 03:38:45.824: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.824: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.824: Got instructions of length 14 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.824: Received command SCAN testprint 178s (process:4408): libfprint-device-DEBUG: 03:38:45.824: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.824: Processing command SCAN testprint 178s (process:4408): libfprint-device-DEBUG: 03:38:45.824: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:4408): libfprint-device-DEBUG: 03:38:45.824: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 178s (process:4408): libfprint-device-DEBUG: 03:38:45.824: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:4408): libfprint-device-DEBUG: 03:38:45.824: Device reported enroll progress, reported 1 of 5 have been completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.824: Sleeping completed 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.824: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.825: Got instructions of length 14 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.825: Received command SCAN testprint 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.825: Processing command SCAN testprint 178s (process:4408): libfprint-device-DEBUG: 03:38:45.825: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 178s (process:4408): libfprint-device-DEBUG: 03:38:45.825: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:4408): libfprint-device-DEBUG: 03:38:45.825: Device reported enroll progress, reported 2 of 5 have been completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.825: Sleeping completed 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.825: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.825: Got instructions of length 14 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.825: Received command SCAN testprint 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.825: Processing command SCAN testprint 178s (process:4408): libfprint-device-DEBUG: 03:38:45.825: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 178s (process:4408): libfprint-device-DEBUG: 03:38:45.825: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:4408): libfprint-device-DEBUG: 03:38:45.825: Device reported enroll progress, reported 3 of 5 have been completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.825: Sleeping completed 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.825: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.825: Got instructions of length 14 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.825: Received command SCAN testprint 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.825: Processing command SCAN testprint 178s (process:4408): libfprint-device-DEBUG: 03:38:45.825: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 178s (process:4408): libfprint-device-DEBUG: 03:38:45.825: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:4408): libfprint-device-DEBUG: 03:38:45.825: Device reported enroll progress, reported 4 of 5 have been completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.825: Sleeping completed 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.826: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.826: Got instructions of length 14 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.826: Received command SCAN testprint 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.826: Processing command SCAN testprint 178s (process:4408): libfprint-device-DEBUG: 03:38:45.826: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 178s (process:4408): libfprint-device-DEBUG: 03:38:45.826: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:4408): libfprint-device-DEBUG: 03:38:45.826: Device reported enroll progress, reported 5 of 5 have been completed 178s (process:4408): libfprint-device-DEBUG: 03:38:45.826: Device reported enroll completion 178s (process:4408): libfprint-device-DEBUG: 03:38:45.826: Device reported finger status change: FP_FINGER_STATUS_NONE 178s (process:4408): libfprint-device-DEBUG: 03:38:45.826: Print for finger FP_FINGER_LEFT_LITTLE enrolled 178s (process:4408): libfprint-device-DEBUG: 03:38:45.826: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 178s (process:4408): libfprint-device-DEBUG: 03:38:45.826: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.826: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.826: Got instructions of length 16 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.826: Received command SET_KEEP_ALIVE 0 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.826: Keep alive toggled: 0 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.826: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.826: Got instructions of length 19 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.826: Received command SET_ENROLL_STAGES 5 178s (process:4408): libfprint-device-DEBUG: 03:38:45.826: Device reported close completion 178s (process:4408): libfprint-device-DEBUG: 03:38:45.826: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 178s (process:4408): libfprint-device-DEBUG: 03:38:45.826: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s Enroll done 178s ok 178s test_enroll_script (__main__.VirtualDevice.test_enroll_script) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.827: 125634718: ../libfprint/drivers/virtual-device.c:387 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.827: 125634739: ../libfprint/drivers/virtual-device-listener.c:153 178s (process:4408): libfprint-device-DEBUG: 03:38:45.827: Device reported open completion 178s (process:4408): libfprint-device-DEBUG: 03:38:45.827: Completing action FPI_DEVICE_ACTION_OPEN in idle! 178s (process:4408): libfprint-device-DEBUG: 03:38:45.827: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.827: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.827: Got instructions of length 19 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.827: Received command SET_ENROLL_STAGES 8 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.827: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.827: Got instructions of length 13 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.827: Received command SCAN print-id 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.827: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.827: Got instructions of length 13 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.827: Received command SCAN print-id 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.827: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.827: Got instructions of length 7 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.827: Received command RETRY 1 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.828: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.828: Got instructions of length 13 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.828: Received command SCAN print-id 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.828: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.828: Got instructions of length 7 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.828: Received command RETRY 3 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.828: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.828: Got instructions of length 13 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.828: Received command SCAN print-id 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.828: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.828: Got instructions of length 7 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.828: Received command RETRY 2 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.828: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.828: Got instructions of length 13 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.828: Received command SCAN print-id 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.829: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.829: Got instructions of length 8 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.829: Received command SLEEP 10 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.829: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.829: Got instructions of length 8 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.829: Received command SLEEP 20 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.829: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.829: Got instructions of length 7 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.829: Received command RETRY 0 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.829: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.829: Got instructions of length 7 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.829: Received command RETRY 3 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.829: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.829: Got instructions of length 13 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.829: Received command SCAN print-id 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.829: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.830: Got instructions of length 15 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.830: Received command SCAN another-id 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.830: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.830: Got instructions of length 13 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.830: Received command SCAN print-id 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.830: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.830: Got instructions of length 13 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.830: Received command SCAN print-id 178s (process:4408): libfprint-device-DEBUG: 03:38:45.830: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.830: Processing command SCAN print-id 178s (process:4408): libfprint-device-DEBUG: 03:38:45.830: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:4408): libfprint-device-DEBUG: 03:38:45.830: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 178s (process:4408): libfprint-device-DEBUG: 03:38:45.830: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:4408): libfprint-device-DEBUG: 03:38:45.830: Device reported enroll progress, reported 1 of 8 have been completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.830: Sleeping completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.830: Processing command SCAN print-id 178s (process:4408): libfprint-device-DEBUG: 03:38:45.830: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 178s (process:4408): libfprint-device-DEBUG: 03:38:45.830: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:4408): libfprint-device-DEBUG: 03:38:45.830: Device reported enroll progress, reported 2 of 8 have been completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.830: Sleeping completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.830: Processing command RETRY 1 178s (process:4408): libfprint-device-DEBUG: 03:38:45.830: Device reported enroll progress, reported 2 of 8 have been completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.830: Sleeping completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.830: Processing command SCAN print-id 178s (process:4408): libfprint-device-DEBUG: 03:38:45.830: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 178s (process:4408): libfprint-device-DEBUG: 03:38:45.830: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:4408): libfprint-device-DEBUG: 03:38:45.830: Device reported enroll progress, reported 3 of 8 have been completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.830: Sleeping completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.830: Processing command RETRY 3 178s (process:4408): libfprint-device-DEBUG: 03:38:45.830: Device reported enroll progress, reported 3 of 8 have been completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.830: Sleeping completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.831: Processing command SCAN print-id 178s (process:4408): libfprint-device-DEBUG: 03:38:45.831: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 178s (process:4408): libfprint-device-DEBUG: 03:38:45.831: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:4408): libfprint-device-DEBUG: 03:38:45.831: Device reported enroll progress, reported 4 of 8 have been completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.831: Sleeping completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.831: Processing command RETRY 2 178s (process:4408): libfprint-device-DEBUG: 03:38:45.831: Device reported enroll progress, reported 4 of 8 have been completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.831: Sleeping completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.831: Processing command SCAN print-id 178s (process:4408): libfprint-device-DEBUG: 03:38:45.831: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 178s (process:4408): libfprint-device-DEBUG: 03:38:45.831: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:4408): libfprint-device-DEBUG: 03:38:45.831: Device reported enroll progress, reported 5 of 8 have been completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.831: Processing command SLEEP 10 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.831: Sleeping 10ms 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.841: Sleeping completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.841: Processing command SLEEP 20 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.841: Sleeping 20ms 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.861: Sleeping completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.861: Processing command RETRY 0 178s (process:4408): libfprint-device-DEBUG: 03:38:45.861: Device reported enroll progress, reported 5 of 8 have been completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.861: Sleeping completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.861: Processing command RETRY 3 178s (process:4408): libfprint-device-DEBUG: 03:38:45.861: Device reported enroll progress, reported 5 of 8 have been completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.861: Sleeping completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.861: Processing command SCAN print-id 178s (process:4408): libfprint-device-DEBUG: 03:38:45.861: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 178s (process:4408): libfprint-device-DEBUG: 03:38:45.861: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:4408): libfprint-device-DEBUG: 03:38:45.861: Device reported enroll progress, reported 6 of 8 have been completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.861: Sleeping completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.861: Processing command SCAN another-id 178s (process:4408): libfprint-device-DEBUG: 03:38:45.861: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 178s (process:4408): libfprint-device-DEBUG: 03:38:45.861: Device reported enroll progress, reported 6 of 8 have been completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.861: Sleeping completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.861: Processing command SCAN print-id 178s (process:4408): libfprint-device-DEBUG: 03:38:45.861: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:4408): libfprint-device-DEBUG: 03:38:45.861: Device reported enroll progress, reported 7 of 8 have been completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.861: Sleeping completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.861: Processing command SCAN print-id 178s (process:4408): libfprint-device-DEBUG: 03:38:45.861: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 178s (process:4408): libfprint-device-DEBUG: 03:38:45.861: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:4408): libfprint-device-DEBUG: 03:38:45.861: Device reported enroll progress, reported 8 of 8 have been completed 178s (process:4408): libfprint-device-DEBUG: 03:38:45.861: Device reported enroll completion 178s (process:4408): libfprint-device-DEBUG: 03:38:45.861: Device reported finger status change: FP_FINGER_STATUS_NONE 178s (process:4408): libfprint-device-DEBUG: 03:38:45.861: Print for finger FP_FINGER_UNKNOWN enrolled 178s (process:4408): libfprint-device-DEBUG: 03:38:45.861: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 178s (process:4408): libfprint-device-DEBUG: 03:38:45.861: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.862: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.862: Got instructions of length 16 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.862: Received command SET_KEEP_ALIVE 0 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.862: Keep alive toggled: 0 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.862: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.862: Got instructions of length 19 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.862: Received command SET_ENROLL_STAGES 5 178s (process:4408): libfprint-device-DEBUG: 03:38:45.862: Device reported close completion 178s (process:4408): libfprint-device-DEBUG: 03:38:45.862: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 178s (process:4408): libfprint-device-DEBUG: 03:38:45.862: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s ok 178s test_enroll_script_interactive (__main__.VirtualDevice.test_enroll_script_interactive) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.862: 125670101: ../libfprint/drivers/virtual-device.c:387 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.862: 125670111: ../libfprint/drivers/virtual-device-listener.c:153 178s (process:4408): libfprint-device-DEBUG: 03:38:45.862: Device reported open completion 178s (process:4408): libfprint-device-DEBUG: 03:38:45.862: Completing action FPI_DEVICE_ACTION_OPEN in idle! 178s (process:4408): libfprint-device-DEBUG: 03:38:45.862: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.862: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.862: Got instructions of length 8 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.862: Received command SLEEP 50 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.862: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.862: Got instructions of length 13 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.862: Received command SCAN print-id 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.862: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.863: Got instructions of length 13 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.863: Received command SCAN print-id 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.863: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.863: Got instructions of length 7 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.863: Received command RETRY 1 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.863: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.863: Got instructions of length 13 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.863: Received command SCAN print-id 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.863: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.863: Got instructions of length 8 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.863: Received command SLEEP 50 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.863: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.863: Got instructions of length 13 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.863: Received command SCAN print-id 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.863: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.863: Got instructions of length 7 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.863: Received command RETRY 2 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.863: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.863: Got instructions of length 15 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.863: Received command SCAN another-id 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.863: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.863: Got instructions of length 13 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.863: Received command SCAN print-id 178s (process:4408): libfprint-device-DEBUG: 03:38:45.864: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.864: Processing command SLEEP 50 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.864: Sleeping 50ms 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.914: Sleeping completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.914: Processing command SCAN print-id 178s (process:4408): libfprint-device-DEBUG: 03:38:45.914: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:4408): libfprint-device-DEBUG: 03:38:45.914: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 178s (process:4408): libfprint-device-DEBUG: 03:38:45.914: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:4408): libfprint-device-DEBUG: 03:38:45.914: Device reported enroll progress, reported 1 of 5 have been completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.914: Sleeping completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.914: Processing command SCAN print-id 178s (process:4408): libfprint-device-DEBUG: 03:38:45.914: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 178s (process:4408): libfprint-device-DEBUG: 03:38:45.914: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:4408): libfprint-device-DEBUG: 03:38:45.914: Device reported enroll progress, reported 2 of 5 have been completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.914: Sleeping completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.914: Processing command RETRY 1 178s (process:4408): libfprint-device-DEBUG: 03:38:45.914: Device reported enroll progress, reported 2 of 5 have been completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.914: Sleeping completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.914: Processing command SCAN print-id 178s (process:4408): libfprint-device-DEBUG: 03:38:45.914: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 178s (process:4408): libfprint-device-DEBUG: 03:38:45.914: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:4408): libfprint-device-DEBUG: 03:38:45.914: Device reported enroll progress, reported 3 of 5 have been completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.914: Processing command SLEEP 50 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.914: Sleeping 50ms 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.964: Sleeping completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.965: Processing command SCAN print-id 178s (process:4408): libfprint-device-DEBUG: 03:38:45.965: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 178s (process:4408): libfprint-device-DEBUG: 03:38:45.965: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:4408): libfprint-device-DEBUG: 03:38:45.965: Device reported enroll progress, reported 4 of 5 have been completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.965: Sleeping completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.965: Processing command RETRY 2 178s (process:4408): libfprint-device-DEBUG: 03:38:45.965: Device reported enroll progress, reported 4 of 5 have been completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.965: Sleeping completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.965: Processing command SCAN another-id 178s (process:4408): libfprint-device-DEBUG: 03:38:45.965: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 178s (process:4408): libfprint-device-DEBUG: 03:38:45.965: Device reported enroll progress, reported 4 of 5 have been completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.965: Sleeping completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.965: Processing command SCAN print-id 178s (process:4408): libfprint-device-DEBUG: 03:38:45.965: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:4408): libfprint-device-DEBUG: 03:38:45.965: Device reported enroll progress, reported 5 of 5 have been completed 178s (process:4408): libfprint-device-DEBUG: 03:38:45.965: Device reported enroll completion 178s (process:4408): libfprint-device-DEBUG: 03:38:45.965: Device reported finger status change: FP_FINGER_STATUS_NONE 178s (process:4408): libfprint-device-DEBUG: 03:38:45.965: Print for finger FP_FINGER_UNKNOWN enrolled 178s (process:4408): libfprint-device-DEBUG: 03:38:45.965: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 178s (process:4408): libfprint-device-DEBUG: 03:38:45.965: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.966: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.966: Got instructions of length 16 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.966: Received command SET_KEEP_ALIVE 0 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.966: Keep alive toggled: 0 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.966: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.966: Got instructions of length 19 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.966: Received command SET_ENROLL_STAGES 5 178s (process:4408): libfprint-device-DEBUG: 03:38:45.966: Device reported close completion 178s (process:4408): libfprint-device-DEBUG: 03:38:45.966: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 178s (process:4408): libfprint-device-DEBUG: 03:38:45.966: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s ok 178s test_enroll_verify_error (__main__.VirtualDevice.test_enroll_verify_error) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.966: 125774309: ../libfprint/drivers/virtual-device.c:387 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.966: 125774332: ../libfprint/drivers/virtual-device-listener.c:153 178s (process:4408): libfprint-device-DEBUG: 03:38:45.966: Device reported open completion 178s (process:4408): libfprint-device-DEBUG: 03:38:45.966: Completing action FPI_DEVICE_ACTION_OPEN in idle! 178s (process:4408): libfprint-device-DEBUG: 03:38:45.966: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.967: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.967: Got instructions of length 14 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.967: Received command SCAN testprint 178s (process:4408): libfprint-device-DEBUG: 03:38:45.967: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.967: Processing command SCAN testprint 178s (process:4408): libfprint-device-DEBUG: 03:38:45.967: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:4408): libfprint-device-DEBUG: 03:38:45.967: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 178s (process:4408): libfprint-device-DEBUG: 03:38:45.967: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:4408): libfprint-device-DEBUG: 03:38:45.967: Device reported enroll progress, reported 1 of 5 have been completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.967: Sleeping completed 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.967: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.967: Got instructions of length 14 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.967: Received command SCAN testprint 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.967: Processing command SCAN testprint 178s (process:4408): libfprint-device-DEBUG: 03:38:45.967: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 178s (process:4408): libfprint-device-DEBUG: 03:38:45.967: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:4408): libfprint-device-DEBUG: 03:38:45.967: Device reported enroll progress, reported 2 of 5 have been completed 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.967: Sleeping completed 178s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.967: Got a new connection! 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.967: Got instructions of length 14 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.967: Received command SCAN testprint 178s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.967: Processing command SCAN testprint 179s (process:4408): libfprint-device-DEBUG: 03:38:45.967: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-device-DEBUG: 03:38:45.967: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:45.967: Device reported enroll progress, reported 3 of 5 have been completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.968: Sleeping completed 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.968: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.968: Got instructions of length 14 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.968: Received command SCAN testprint 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.968: Processing command SCAN testprint 179s (process:4408): libfprint-device-DEBUG: 03:38:45.968: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-device-DEBUG: 03:38:45.968: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:45.968: Device reported enroll progress, reported 4 of 5 have been completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.968: Sleeping completed 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.968: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.968: Got instructions of length 14 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.968: Received command SCAN testprint 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.968: Processing command SCAN testprint 179s (process:4408): libfprint-device-DEBUG: 03:38:45.968: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-device-DEBUG: 03:38:45.968: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:45.968: Device reported enroll progress, reported 5 of 5 have been completed 179s (process:4408): libfprint-device-DEBUG: 03:38:45.968: Device reported enroll completion 179s (process:4408): libfprint-device-DEBUG: 03:38:45.968: Device reported finger status change: FP_FINGER_STATUS_NONE 179s (process:4408): libfprint-device-DEBUG: 03:38:45.968: Print for finger FP_FINGER_LEFT_RING enrolled 179s (process:4408): libfprint-device-DEBUG: 03:38:45.968: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:45.968: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.969: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.969: Got instructions of length 7 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.969: Received command ERROR 0 179s (process:4408): libfprint-device-DEBUG: 03:38:45.969: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.969: Processing command ERROR 0 179s (process:4408): libfprint-device-DEBUG: 03:38:45.969: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.969: Virtual device scan failed with error: An unspecified error occurred! 179s (process:4408): libfprint-device-DEBUG: 03:38:45.969: Device reported verify completion 179s (process:4408): libfprint-device-DEBUG: 03:38:45.969: Device reported finger status change: FP_FINGER_STATUS_NONE 179s (process:4408): libfprint-device-DEBUG: 03:38:45.969: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:45.969: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.969: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.969: Got instructions of length 16 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.969: Received command SET_KEEP_ALIVE 0 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.969: Keep alive toggled: 0 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.969: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.969: Got instructions of length 19 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.969: Received command SET_ENROLL_STAGES 5 179s (process:4408): libfprint-device-DEBUG: 03:38:45.969: Device reported close completion 179s (process:4408): libfprint-device-DEBUG: 03:38:45.969: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:45.969: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s Enroll done 179s ok 179s test_enroll_verify_match (__main__.VirtualDevice.test_enroll_verify_match) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.970: 125777727: ../libfprint/drivers/virtual-device.c:387 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.970: 125777750: ../libfprint/drivers/virtual-device-listener.c:153 179s (process:4408): libfprint-device-DEBUG: 03:38:45.970: Device reported open completion 179s (process:4408): libfprint-device-DEBUG: 03:38:45.970: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:45.970: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.970: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.970: Got instructions of length 14 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.970: Received command SCAN testprint 179s (process:4408): libfprint-device-DEBUG: 03:38:45.970: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.970: Processing command SCAN testprint 179s (process:4408): libfprint-device-DEBUG: 03:38:45.970: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:45.970: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-device-DEBUG: 03:38:45.970: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:45.970: Device reported enroll progress, reported 1 of 5 have been completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.970: Sleeping completed 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.970: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.970: Got instructions of length 14 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.970: Received command SCAN testprint 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.970: Processing command SCAN testprint 179s (process:4408): libfprint-device-DEBUG: 03:38:45.970: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-device-DEBUG: 03:38:45.970: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:45.970: Device reported enroll progress, reported 2 of 5 have been completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.971: Sleeping completed 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.971: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.971: Got instructions of length 14 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.971: Received command SCAN testprint 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.971: Processing command SCAN testprint 179s (process:4408): libfprint-device-DEBUG: 03:38:45.971: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-device-DEBUG: 03:38:45.971: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:45.971: Device reported enroll progress, reported 3 of 5 have been completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.971: Sleeping completed 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.971: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.971: Got instructions of length 14 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.971: Received command SCAN testprint 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.971: Processing command SCAN testprint 179s (process:4408): libfprint-device-DEBUG: 03:38:45.971: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-device-DEBUG: 03:38:45.971: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:45.971: Device reported enroll progress, reported 4 of 5 have been completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.971: Sleeping completed 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.971: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.971: Got instructions of length 14 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.971: Received command SCAN testprint 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.972: Processing command SCAN testprint 179s (process:4408): libfprint-device-DEBUG: 03:38:45.972: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-device-DEBUG: 03:38:45.972: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:45.972: Device reported enroll progress, reported 5 of 5 have been completed 179s (process:4408): libfprint-device-DEBUG: 03:38:45.972: Device reported enroll completion 179s (process:4408): libfprint-device-DEBUG: 03:38:45.972: Device reported finger status change: FP_FINGER_STATUS_NONE 179s (process:4408): libfprint-device-DEBUG: 03:38:45.972: Print for finger FP_FINGER_LEFT_THUMB enrolled 179s (process:4408): libfprint-device-DEBUG: 03:38:45.972: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:45.972: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.972: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.972: Got instructions of length 14 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.972: Received command SCAN testprint 179s (process:4408): libfprint-device-DEBUG: 03:38:45.972: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.972: Processing command SCAN testprint 179s (process:4408): libfprint-device-DEBUG: 03:38:45.972: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:45.972: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.972: Virtual device scanned print testprint 179s (process:4408): libfprint-device-DEBUG: 03:38:45.972: Device reported verify result 179s (process:4408): libfprint-device-DEBUG: 03:38:45.972: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:45.972: Device reported verify completion 179s (process:4408): libfprint-device-DEBUG: 03:38:45.972: Device reported finger status change: FP_FINGER_STATUS_NONE 179s (process:4408): libfprint-device-DEBUG: 03:38:45.972: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:45.972: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.973: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.973: Got instructions of length 16 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.973: Received command SET_KEEP_ALIVE 0 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.973: Keep alive toggled: 0 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.973: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.973: Got instructions of length 19 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.973: Received command SET_ENROLL_STAGES 5 179s (process:4408): libfprint-device-DEBUG: 03:38:45.973: Device reported close completion 179s (process:4408): libfprint-device-DEBUG: 03:38:45.973: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:45.973: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s Enroll done 179s ok 179s test_enroll_verify_no_match (__main__.VirtualDevice.test_enroll_verify_no_match) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.973: 125781206: ../libfprint/drivers/virtual-device.c:387 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.973: 125781229: ../libfprint/drivers/virtual-device-listener.c:153 179s (process:4408): libfprint-device-DEBUG: 03:38:45.973: Device reported open completion 179s (process:4408): libfprint-device-DEBUG: 03:38:45.973: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:45.973: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.973: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.973: Got instructions of length 14 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.973: Received command SCAN testprint 179s (process:4408): libfprint-device-DEBUG: 03:38:45.974: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.974: Processing command SCAN testprint 179s (process:4408): libfprint-device-DEBUG: 03:38:45.974: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:45.974: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-device-DEBUG: 03:38:45.974: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:45.974: Device reported enroll progress, reported 1 of 5 have been completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.974: Sleeping completed 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.974: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.974: Got instructions of length 14 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.974: Received command SCAN testprint 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.974: Processing command SCAN testprint 179s (process:4408): libfprint-device-DEBUG: 03:38:45.974: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-device-DEBUG: 03:38:45.974: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:45.974: Device reported enroll progress, reported 2 of 5 have been completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.974: Sleeping completed 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.974: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.974: Got instructions of length 14 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.974: Received command SCAN testprint 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.974: Processing command SCAN testprint 179s (process:4408): libfprint-device-DEBUG: 03:38:45.974: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-device-DEBUG: 03:38:45.974: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:45.974: Device reported enroll progress, reported 3 of 5 have been completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.974: Sleeping completed 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.974: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.975: Got instructions of length 14 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.975: Received command SCAN testprint 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.975: Processing command SCAN testprint 179s (process:4408): libfprint-device-DEBUG: 03:38:45.975: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-device-DEBUG: 03:38:45.975: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:45.975: Device reported enroll progress, reported 4 of 5 have been completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.975: Sleeping completed 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.975: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.975: Got instructions of length 14 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.975: Received command SCAN testprint 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.975: Processing command SCAN testprint 179s (process:4408): libfprint-device-DEBUG: 03:38:45.975: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-device-DEBUG: 03:38:45.975: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:45.975: Device reported enroll progress, reported 5 of 5 have been completed 179s (process:4408): libfprint-device-DEBUG: 03:38:45.975: Device reported enroll completion 179s (process:4408): libfprint-device-DEBUG: 03:38:45.975: Device reported finger status change: FP_FINGER_STATUS_NONE 179s (process:4408): libfprint-device-DEBUG: 03:38:45.975: Print for finger FP_FINGER_LEFT_RING enrolled 179s (process:4408): libfprint-device-DEBUG: 03:38:45.975: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:45.975: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.975: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.975: Got instructions of length 18 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.975: Received command SCAN not-testprint 179s (process:4408): libfprint-device-DEBUG: 03:38:45.975: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.975: Processing command SCAN not-testprint 179s (process:4408): libfprint-device-DEBUG: 03:38:45.975: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:45.976: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.976: Virtual device scanned print not-testprint 179s (process:4408): libfprint-device-DEBUG: 03:38:45.976: Device reported verify result 179s (process:4408): libfprint-device-DEBUG: 03:38:45.976: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:45.976: Device reported verify completion 179s (process:4408): libfprint-device-DEBUG: 03:38:45.976: Device reported finger status change: FP_FINGER_STATUS_NONE 179s (process:4408): libfprint-device-DEBUG: 03:38:45.976: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:45.976: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.976: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.976: Got instructions of length 16 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.976: Received command SET_KEEP_ALIVE 0 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.976: Keep alive toggled: 0 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.976: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.976: Got instructions of length 19 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.976: Received command SET_ENROLL_STAGES 5 179s (process:4408): libfprint-device-DEBUG: 03:38:45.976: Device reported close completion 179s (process:4408): libfprint-device-DEBUG: 03:38:45.976: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:45.976: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s Enroll done 179s ok 179s test_enroll_verify_retry (__main__.VirtualDevice.test_enroll_verify_retry) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.976: 125784503: ../libfprint/drivers/virtual-device.c:387 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.976: 125784524: ../libfprint/drivers/virtual-device-listener.c:153 179s (process:4408): libfprint-device-DEBUG: 03:38:45.976: Device reported open completion 179s (process:4408): libfprint-device-DEBUG: 03:38:45.977: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:45.977: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.977: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.977: Got instructions of length 7 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.977: Received command RETRY 1 179s (process:4408): libfprint-device-DEBUG: 03:38:45.977: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.977: Processing command RETRY 1 179s (process:4408): libfprint-device-DEBUG: 03:38:45.977: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.977: Virtual device scan failed with error: The swipe was too short, please try again. 179s (process:4408): libfprint-device-DEBUG: 03:38:45.977: Device reported verify result 179s (process:4408): libfprint-device-DEBUG: 03:38:45.977: Device reported verify completion 179s (process:4408): libfprint-device-DEBUG: 03:38:45.977: Device reported finger status change: FP_FINGER_STATUS_NONE 179s (process:4408): libfprint-device-DEBUG: 03:38:45.977: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:45.977: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.977: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.977: Got instructions of length 16 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.977: Received command SET_KEEP_ALIVE 0 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.977: Keep alive toggled: 0 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.977: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.977: Got instructions of length 19 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.977: Received command SET_ENROLL_STAGES 5 179s (process:4408): libfprint-device-DEBUG: 03:38:45.978: Device reported close completion 179s (process:4408): libfprint-device-DEBUG: 03:38:45.978: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:45.978: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s ok 179s test_enroll_verify_script (__main__.VirtualDevice.test_enroll_verify_script) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.978: 125785816: ../libfprint/drivers/virtual-device.c:387 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.978: 125785837: ../libfprint/drivers/virtual-device-listener.c:153 179s (process:4408): libfprint-device-DEBUG: 03:38:45.978: Device reported open completion 179s (process:4408): libfprint-device-DEBUG: 03:38:45.978: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:45.978: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.978: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.978: Got instructions of length 19 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.978: Received command SET_ENROLL_STAGES 8 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.978: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.978: Got instructions of length 13 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.978: Received command SCAN print-id 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.978: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.978: Got instructions of length 13 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.978: Received command SCAN print-id 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.979: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.979: Got instructions of length 7 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.979: Received command RETRY 1 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.979: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.979: Got instructions of length 13 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.979: Received command SCAN print-id 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.979: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.979: Got instructions of length 7 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.979: Received command RETRY 3 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.979: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.979: Got instructions of length 13 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.979: Received command SCAN print-id 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.979: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.979: Got instructions of length 7 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.979: Received command RETRY 2 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.979: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.980: Got instructions of length 13 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.980: Received command SCAN print-id 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.980: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.980: Got instructions of length 8 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.980: Received command SLEEP 10 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.980: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.980: Got instructions of length 8 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.980: Received command SLEEP 20 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.980: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.980: Got instructions of length 7 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.980: Received command RETRY 0 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.980: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.980: Got instructions of length 7 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.980: Received command RETRY 3 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.980: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.980: Got instructions of length 13 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.980: Received command SCAN print-id 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.981: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.981: Got instructions of length 15 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.981: Received command SCAN another-id 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.981: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.981: Got instructions of length 13 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.981: Received command SCAN print-id 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:45.981: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.981: Got instructions of length 13 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.981: Received command SCAN print-id 179s (process:4408): libfprint-device-DEBUG: 03:38:45.981: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.981: Processing command SCAN print-id 179s (process:4408): libfprint-device-DEBUG: 03:38:45.981: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:45.981: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-device-DEBUG: 03:38:45.981: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:45.981: Device reported enroll progress, reported 1 of 8 have been completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.981: Sleeping completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.981: Processing command SCAN print-id 179s (process:4408): libfprint-device-DEBUG: 03:38:45.981: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-device-DEBUG: 03:38:45.981: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:45.981: Device reported enroll progress, reported 2 of 8 have been completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.981: Sleeping completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.981: Processing command RETRY 1 179s (process:4408): libfprint-device-DEBUG: 03:38:45.981: Device reported enroll progress, reported 2 of 8 have been completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.981: Sleeping completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.981: Processing command SCAN print-id 179s (process:4408): libfprint-device-DEBUG: 03:38:45.981: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-device-DEBUG: 03:38:45.981: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:45.981: Device reported enroll progress, reported 3 of 8 have been completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.981: Sleeping completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.981: Processing command RETRY 3 179s (process:4408): libfprint-device-DEBUG: 03:38:45.981: Device reported enroll progress, reported 3 of 8 have been completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.982: Sleeping completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.982: Processing command SCAN print-id 179s (process:4408): libfprint-device-DEBUG: 03:38:45.982: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-device-DEBUG: 03:38:45.982: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:45.982: Device reported enroll progress, reported 4 of 8 have been completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.982: Sleeping completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.982: Processing command RETRY 2 179s (process:4408): libfprint-device-DEBUG: 03:38:45.982: Device reported enroll progress, reported 4 of 8 have been completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.982: Sleeping completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.982: Processing command SCAN print-id 179s (process:4408): libfprint-device-DEBUG: 03:38:45.982: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-device-DEBUG: 03:38:45.982: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:45.982: Device reported enroll progress, reported 5 of 8 have been completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.982: Processing command SLEEP 10 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.982: Sleeping 10ms 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.992: Sleeping completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.992: Processing command SLEEP 20 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:45.992: Sleeping 20ms 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.012: Sleeping completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.012: Processing command RETRY 0 179s (process:4408): libfprint-device-DEBUG: 03:38:46.012: Device reported enroll progress, reported 5 of 8 have been completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.012: Sleeping completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.012: Processing command RETRY 3 179s (process:4408): libfprint-device-DEBUG: 03:38:46.012: Device reported enroll progress, reported 5 of 8 have been completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.012: Sleeping completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.012: Processing command SCAN print-id 179s (process:4408): libfprint-device-DEBUG: 03:38:46.012: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-device-DEBUG: 03:38:46.012: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:46.012: Device reported enroll progress, reported 6 of 8 have been completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.012: Sleeping completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.012: Processing command SCAN another-id 179s (process:4408): libfprint-device-DEBUG: 03:38:46.012: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-device-DEBUG: 03:38:46.012: Device reported enroll progress, reported 6 of 8 have been completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.012: Sleeping completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.012: Processing command SCAN print-id 179s (process:4408): libfprint-device-DEBUG: 03:38:46.012: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:46.012: Device reported enroll progress, reported 7 of 8 have been completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.012: Sleeping completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.012: Processing command SCAN print-id 179s (process:4408): libfprint-device-DEBUG: 03:38:46.012: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-device-DEBUG: 03:38:46.012: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:46.012: Device reported enroll progress, reported 8 of 8 have been completed 179s (process:4408): libfprint-device-DEBUG: 03:38:46.012: Device reported enroll completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.012: Device reported finger status change: FP_FINGER_STATUS_NONE 179s (process:4408): libfprint-device-DEBUG: 03:38:46.012: Print for finger FP_FINGER_UNKNOWN enrolled 179s (process:4408): libfprint-device-DEBUG: 03:38:46.012: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.012: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.013: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.013: Got instructions of length 7 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.013: Received command RETRY 2 179s (process:4408): libfprint-device-DEBUG: 03:38:46.013: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.013: Processing command RETRY 2 179s (process:4408): libfprint-device-DEBUG: 03:38:46.013: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.013: Virtual device scan failed with error: The finger was not centered properly, please try again. 179s (process:4408): libfprint-device-DEBUG: 03:38:46.013: Device reported verify result 179s (process:4408): libfprint-device-DEBUG: 03:38:46.013: Device reported verify completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.013: Device reported finger status change: FP_FINGER_STATUS_NONE 179s (process:4408): libfprint-device-DEBUG: 03:38:46.013: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.013: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.013: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.013: Got instructions of length 8 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.013: Received command SLEEP 50 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.013: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.013: Got instructions of length 7 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.013: Received command RETRY 1 179s (process:4408): libfprint-device-DEBUG: 03:38:46.013: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.013: Processing command SLEEP 50 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.013: Sleeping 50ms 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.064: Sleeping completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.064: Processing command RETRY 1 179s (process:4408): libfprint-device-DEBUG: 03:38:46.064: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.064: Virtual device scan failed with error: The swipe was too short, please try again. 179s (process:4408): libfprint-device-DEBUG: 03:38:46.064: Device reported verify result 179s (process:4408): libfprint-device-DEBUG: 03:38:46.064: Device reported verify completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.064: Device reported finger status change: FP_FINGER_STATUS_NONE 179s (process:4408): libfprint-device-DEBUG: 03:38:46.064: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.064: Updated temperature model after 0.05 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.064: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.064: Got instructions of length 15 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.064: Received command SCAN another-id 179s (process:4408): libfprint-device-DEBUG: 03:38:46.064: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.064: Processing command SCAN another-id 179s (process:4408): libfprint-device-DEBUG: 03:38:46.064: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:46.064: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.064: Virtual device scanned print another-id 179s (process:4408): libfprint-device-DEBUG: 03:38:46.064: Device reported verify result 179s (process:4408): libfprint-device-DEBUG: 03:38:46.064: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:46.064: Device reported verify completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.064: Device reported finger status change: FP_FINGER_STATUS_NONE 179s (process:4408): libfprint-device-DEBUG: 03:38:46.064: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.064: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.064: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.064: Got instructions of length 13 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.064: Received command SCAN print-id 179s (process:4408): libfprint-device-DEBUG: 03:38:46.064: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.064: Processing command SCAN print-id 179s (process:4408): libfprint-device-DEBUG: 03:38:46.064: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:46.064: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.064: Virtual device scanned print print-id 179s (process:4408): libfprint-device-DEBUG: 03:38:46.065: Device reported verify result 179s (process:4408): libfprint-device-DEBUG: 03:38:46.065: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:46.065: Device reported verify completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.065: Device reported finger status change: FP_FINGER_STATUS_NONE 179s (process:4408): libfprint-device-DEBUG: 03:38:46.065: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.065: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.065: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.065: Got instructions of length 16 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.065: Received command SET_KEEP_ALIVE 0 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.065: Keep alive toggled: 0 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.065: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.065: Got instructions of length 19 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.065: Received command SET_ENROLL_STAGES 5 179s (process:4408): libfprint-device-DEBUG: 03:38:46.065: Device reported close completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.065: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.065: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s ok 179s test_enroll_with_retry (__main__.VirtualDevice.test_enroll_with_retry) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.065: 125873235: ../libfprint/drivers/virtual-device.c:387 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.065: 125873248: ../libfprint/drivers/virtual-device-listener.c:153 179s (process:4408): libfprint-device-DEBUG: 03:38:46.065: Device reported open completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.065: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.065: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.065: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.065: Got instructions of length 14 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.065: Received command SCAN testprint 179s (process:4408): libfprint-device-DEBUG: 03:38:46.066: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.066: Processing command SCAN testprint 179s (process:4408): libfprint-device-DEBUG: 03:38:46.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:46.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-device-DEBUG: 03:38:46.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:46.066: Device reported enroll progress, reported 1 of 5 have been completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.066: Sleeping completed 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.066: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.066: Got instructions of length 14 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.066: Received command SCAN testprint 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.066: Processing command SCAN testprint 179s (process:4408): libfprint-device-DEBUG: 03:38:46.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-device-DEBUG: 03:38:46.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:46.066: Device reported enroll progress, reported 2 of 5 have been completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.066: Sleeping completed 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.066: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.066: Got instructions of length 7 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.066: Received command RETRY 1 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.066: Processing command RETRY 1 179s (process:4408): libfprint-device-DEBUG: 03:38:46.066: Device reported enroll progress, reported 2 of 5 have been completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.066: Sleeping completed 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.066: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.066: Got instructions of length 14 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.066: Received command SCAN testprint 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.066: Processing command SCAN testprint 179s (process:4408): libfprint-device-DEBUG: 03:38:46.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-device-DEBUG: 03:38:46.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:46.066: Device reported enroll progress, reported 3 of 5 have been completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.067: Sleeping completed 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.067: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.067: Got instructions of length 14 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.067: Received command SCAN testprint 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.067: Processing command SCAN testprint 179s (process:4408): libfprint-device-DEBUG: 03:38:46.067: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-device-DEBUG: 03:38:46.067: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:46.067: Device reported enroll progress, reported 4 of 5 have been completed 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.067: Sleeping completed 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.067: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.067: Got instructions of length 14 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.067: Received command SCAN testprint 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.067: Processing command SCAN testprint 179s (process:4408): libfprint-device-DEBUG: 03:38:46.067: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-device-DEBUG: 03:38:46.067: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:46.067: Device reported enroll progress, reported 5 of 5 have been completed 179s (process:4408): libfprint-device-DEBUG: 03:38:46.067: Device reported enroll completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.067: Device reported finger status change: FP_FINGER_STATUS_NONE 179s (process:4408): libfprint-device-DEBUG: 03:38:46.067: Print for finger FP_FINGER_LEFT_LITTLE enrolled 179s (process:4408): libfprint-device-DEBUG: 03:38:46.067: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.067: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.067: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.067: Got instructions of length 16 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.067: Received command SET_KEEP_ALIVE 0 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.067: Keep alive toggled: 0 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.068: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.068: Got instructions of length 19 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.068: Received command SET_ENROLL_STAGES 5 179s (process:4408): libfprint-device-DEBUG: 03:38:46.068: Device reported close completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.068: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.068: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s Enroll done 179s ok 179s test_finger_status (__main__.VirtualDevice.test_finger_status) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.068: 125875860: ../libfprint/drivers/virtual-device.c:387 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.068: 125875870: ../libfprint/drivers/virtual-device-listener.c:153 179s (process:4408): libfprint-device-DEBUG: 03:38:46.068: Device reported open completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.068: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.068: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-device-DEBUG: 03:38:46.068: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-device-DEBUG: 03:38:46.068: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.068: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.068: Got instructions of length 8 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.068: Received command FINGER 1 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.068: Processing command FINGER 1 179s (process:4408): libfprint-device-DEBUG: 03:38:46.068: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.068: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.068: Got instructions of length 8 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.068: Received command FINGER 0 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.068: Processing command FINGER 0 179s (process:4408): libfprint-device-DEBUG: 03:38:46.068: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:46.068: Idle cancelling on ongoing operation! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.068: Got cancellation! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.068: Virtual device scan failed with error: Operation was cancelled 179s (process:4408): libfprint-device-DEBUG: 03:38:46.068: Device reported verify completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.068: Device reported finger status change: FP_FINGER_STATUS_NONE 179s (process:4408): libfprint-device-DEBUG: 03:38:46.068: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.068: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.069: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.069: Got instructions of length 16 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.069: Received command SET_KEEP_ALIVE 0 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.069: Keep alive toggled: 0 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.069: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.069: Got instructions of length 19 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.069: Received command SET_ENROLL_STAGES 5 179s (process:4408): libfprint-device-DEBUG: 03:38:46.069: Device reported close completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.069: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.069: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s ok 179s test_finger_status_after_sleep (__main__.VirtualDevice.test_finger_status_after_sleep) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.069: 125877090: ../libfprint/drivers/virtual-device.c:387 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.069: 125877101: ../libfprint/drivers/virtual-device-listener.c:153 179s (process:4408): libfprint-device-DEBUG: 03:38:46.069: Device reported open completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.069: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.069: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.069: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.069: Got instructions of length 8 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.069: Received command SLEEP 10 179s (process:4408): libfprint-device-DEBUG: 03:38:46.069: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.069: Processing command SLEEP 10 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.069: Sleeping 10ms 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.079: Sleeping completed 179s (process:4408): libfprint-device-DEBUG: 03:38:46.079: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.080: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.080: Got instructions of length 8 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.080: Received command FINGER 1 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.080: Processing command FINGER 1 179s (process:4408): libfprint-device-DEBUG: 03:38:46.080: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.080: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.080: Got instructions of length 8 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.080: Received command FINGER 0 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.080: Processing command FINGER 0 179s (process:4408): libfprint-device-DEBUG: 03:38:46.080: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:46.080: Idle cancelling on ongoing operation! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.080: Got cancellation! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.080: Virtual device scan failed with error: Operation was cancelled 179s (process:4408): libfprint-device-DEBUG: 03:38:46.080: Device reported verify completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.080: Device reported finger status change: FP_FINGER_STATUS_NONE 179s (process:4408): libfprint-device-DEBUG: 03:38:46.080: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.080: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.080: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.080: Got instructions of length 16 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.080: Received command SET_KEEP_ALIVE 0 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.080: Keep alive toggled: 0 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.080: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.080: Got instructions of length 19 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.080: Received command SET_ENROLL_STAGES 5 179s (process:4408): libfprint-device-DEBUG: 03:38:46.080: Device reported close completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.080: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.080: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s ok 179s test_identify_unsupported (__main__.VirtualDevice.test_identify_unsupported) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.081: 125888685: ../libfprint/drivers/virtual-device.c:387 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.081: 125888695: ../libfprint/drivers/virtual-device-listener.c:153 179s (process:4408): libfprint-device-DEBUG: 03:38:46.081: Device reported open completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.081: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.081: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.081: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.081: Got instructions of length 16 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.081: Received command SET_KEEP_ALIVE 0 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.081: Keep alive toggled: 0 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.081: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.081: Got instructions of length 19 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.081: Received command SET_ENROLL_STAGES 5 179s (process:4408): libfprint-device-DEBUG: 03:38:46.081: Device reported close completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.081: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.081: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s ok 179s test_open_error (__main__.VirtualDevice.test_open_error) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.081: 125889466: ../libfprint/drivers/virtual-device.c:387 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.081: 125889477: ../libfprint/drivers/virtual-device-listener.c:153 179s (process:4408): libfprint-device-DEBUG: 03:38:46.081: Device reported open completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.081: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.081: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.082: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.082: Got instructions of length 16 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.082: Received command IGNORED_COMMAND 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.082: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.082: Got instructions of length 7 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.082: Received command ERROR 5 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.082: Processing command IGNORED_COMMAND 179s (process:4408): libfprint-device-DEBUG: 03:38:46.082: Device reported close completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.082: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.082: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.082: 125890161: ../libfprint/drivers/virtual-device.c:387 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.082: Processing command ERROR 5 179s (process:4408): libfprint-device-DEBUG: 03:38:46.082: Device reported open completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.082: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.082: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s ok 179s test_open_error_with_keep_alive (__main__.VirtualDevice.test_open_error_with_keep_alive) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.082: 125890302: ../libfprint/drivers/virtual-device.c:387 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.082: 125890313: ../libfprint/drivers/virtual-device-listener.c:153 179s (process:4408): libfprint-device-DEBUG: 03:38:46.082: Device reported open completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.082: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.082: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.082: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.082: Got instructions of length 16 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.082: Received command SET_KEEP_ALIVE 1 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.082: Keep alive toggled: 1 179s (process:4408): libfprint-device-DEBUG: 03:38:46.082: Device reported close completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.082: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.083: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.083: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.083: Got instructions of length 7 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.083: Received command ERROR 5 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.083: 125890809: ../libfprint/drivers/virtual-device.c:387 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.083: Processing command ERROR 5 179s (process:4408): libfprint-device-DEBUG: 03:38:46.083: Device reported open completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.083: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.083: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s ok 179s test_quick_enroll (__main__.VirtualDevice.test_quick_enroll) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.083: 125890930: ../libfprint/drivers/virtual-device.c:387 179s (process:4408): libfprint-device-DEBUG: 03:38:46.083: Device reported open completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.083: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.083: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.083: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.083: Got instructions of length 19 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.083: Received command SET_ENROLL_STAGES 1 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.083: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.083: Got instructions of length 14 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.083: Received command SCAN testprint 179s (process:4408): libfprint-device-DEBUG: 03:38:46.083: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.083: Processing command SCAN testprint 179s (process:4408): libfprint-device-DEBUG: 03:38:46.083: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:46.083: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:4408): libfprint-device-DEBUG: 03:38:46.083: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:4408): libfprint-device-DEBUG: 03:38:46.083: Device reported enroll progress, reported 1 of 1 have been completed 179s (process:4408): libfprint-device-DEBUG: 03:38:46.083: Device reported enroll completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.083: Device reported finger status change: FP_FINGER_STATUS_NONE 179s (process:4408): libfprint-device-DEBUG: 03:38:46.083: Print for finger FP_FINGER_LEFT_LITTLE enrolled 179s (process:4408): libfprint-device-DEBUG: 03:38:46.083: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.083: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.084: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.084: Got instructions of length 16 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.084: Received command SET_KEEP_ALIVE 0 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.084: Keep alive toggled: 0 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.084: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.084: Got instructions of length 19 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.084: Received command SET_ENROLL_STAGES 5 179s (process:4408): libfprint-device-DEBUG: 03:38:46.084: Device reported close completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.084: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.084: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s Enroll done 179s ok 179s (process:4408): libfprint-context-DEBUG: 03:38:46.085: Initializing FpContext (libfprint version 1.94.8+tod1) 179s (process:4408): libfprint-tod-DEBUG: 03:38:46.085: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 179s (process:4408): libfprint-context-DEBUG: 03:38:46.087: No driver found for USB device 1D6B:0003 179s (process:4408): libfprint-context-DEBUG: 03:38:46.087: No driver found for USB device 0627:0001 179s (process:4408): libfprint-context-DEBUG: 03:38:46.087: No driver found for USB device 0627:0001 179s (process:4408): libfprint-context-DEBUG: 03:38:46.087: No driver found for USB device 1D6B:0002 179s (process:4408): libfprint-context-DEBUG: 03:38:46.087: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-8_8fn1bc/virtual-device.socket 179s (process:4408): libfprint-context-DEBUG: 03:38:46.087: created 179s (process:4408): libfprint-device-DEBUG: 03:38:46.089: Device reported probe completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.089: Completing action FPI_DEVICE_ACTION_PROBE in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.089: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s test_capture (__main__.VirtualDeviceBusyDeviceOperations.test_capture) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.089: 125897077: ../libfprint/drivers/virtual-device.c:387 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.089: 125897087: ../libfprint/drivers/virtual-device-listener.c:153 179s (process:4408): libfprint-device-DEBUG: 03:38:46.089: Device reported open completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.089: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.089: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.089: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.089: Got instructions of length 9 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.089: Received command SLEEP 200 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.089: Processing command SLEEP 200 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.089: Sleeping 200ms 179s Executing: libfprint-2/virtual-device.test 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.290: Sleeping completed 179s (process:4408): libfprint-device-DEBUG: 03:38:46.290: Device reported close completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.290: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.290: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s ok 179s test_close (__main__.VirtualDeviceBusyDeviceOperations.test_close) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.290: 126098047: ../libfprint/drivers/virtual-device.c:387 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.290: 126098060: ../libfprint/drivers/virtual-device-listener.c:153 179s (process:4408): libfprint-device-DEBUG: 03:38:46.290: Device reported open completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.290: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.290: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.290: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.290: Got instructions of length 9 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.290: Received command SLEEP 200 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.290: Processing command SLEEP 200 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.290: Sleeping 200ms 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.491: Sleeping completed 179s (process:4408): libfprint-device-DEBUG: 03:38:46.491: Device reported close completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.491: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.491: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s ok 179s test_delete_print (__main__.VirtualDeviceBusyDeviceOperations.test_delete_print) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.491: 126299392: ../libfprint/drivers/virtual-device.c:387 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.491: 126299404: ../libfprint/drivers/virtual-device-listener.c:153 179s (process:4408): libfprint-device-DEBUG: 03:38:46.491: Device reported open completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.491: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.491: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.492: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.492: Got instructions of length 9 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.492: Received command SLEEP 200 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.492: Processing command SLEEP 200 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.492: Sleeping 200ms 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.692: Sleeping completed 179s (process:4408): libfprint-device-DEBUG: 03:38:46.692: Device reported close completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.692: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.692: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s ok 179s test_enroll (__main__.VirtualDeviceBusyDeviceOperations.test_enroll) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.692: 126500474: ../libfprint/drivers/virtual-device.c:387 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.692: 126500486: ../libfprint/drivers/virtual-device-listener.c:153 179s (process:4408): libfprint-device-DEBUG: 03:38:46.692: Device reported open completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.693: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.693: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.693: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.693: Got instructions of length 9 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.693: Received command SLEEP 200 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.693: Processing command SLEEP 200 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.693: Sleeping 200ms 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.893: Sleeping completed 179s (process:4408): libfprint-device-DEBUG: 03:38:46.893: Device reported close completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.893: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.893: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s ok 179s test_identify (__main__.VirtualDeviceBusyDeviceOperations.test_identify) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.893: 126701511: ../libfprint/drivers/virtual-device.c:387 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.893: 126701523: ../libfprint/drivers/virtual-device-listener.c:153 179s (process:4408): libfprint-device-DEBUG: 03:38:46.894: Device reported open completion 179s (process:4408): libfprint-device-DEBUG: 03:38:46.894: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s (process:4408): libfprint-device-DEBUG: 03:38:46.894: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:46.894: Got a new connection! 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.894: Got instructions of length 9 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.894: Received command SLEEP 200 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.894: Processing command SLEEP 200 179s (process:4408): libfprint-virtual_device-DEBUG: 03:38:46.894: Sleeping 200ms 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.094: Sleeping completed 180s (process:4408): libfprint-device-DEBUG: 03:38:47.094: Device reported close completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.094: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.094: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s ok 180s test_list_prints (__main__.VirtualDeviceBusyDeviceOperations.test_list_prints) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.094: 126902571: ../libfprint/drivers/virtual-device.c:387 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.094: 126902582: ../libfprint/drivers/virtual-device-listener.c:153 180s (process:4408): libfprint-device-DEBUG: 03:38:47.095: Device reported open completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.095: Completing action FPI_DEVICE_ACTION_OPEN in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.095: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.095: Got a new connection! 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.095: Got instructions of length 9 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.095: Received command SLEEP 200 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.095: Processing command SLEEP 200 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.095: Sleeping 200ms 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.295: Sleeping completed 180s (process:4408): libfprint-device-DEBUG: 03:38:47.295: Device reported close completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.295: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.295: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s ok 180s test_open (__main__.VirtualDeviceBusyDeviceOperations.test_open) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.296: 127103690: ../libfprint/drivers/virtual-device.c:387 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.296: 127103704: ../libfprint/drivers/virtual-device-listener.c:153 180s (process:4408): libfprint-device-DEBUG: 03:38:47.296: Device reported open completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.296: Completing action FPI_DEVICE_ACTION_OPEN in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.296: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.296: Got a new connection! 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.296: Got instructions of length 9 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.296: Received command SLEEP 200 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.296: Processing command SLEEP 200 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.296: Sleeping 200ms 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.296: Got a new connection! 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.296: Got instructions of length 16 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.296: Received command SET_KEEP_ALIVE 1 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.296: Keep alive toggled: 1 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.496: Sleeping completed 180s (process:4408): libfprint-device-DEBUG: 03:38:47.496: Device reported close completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.497: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.497: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.497: Got a new connection! 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.497: Got instructions of length 9 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.497: Received command SLEEP 100 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.497: 127305025: ../libfprint/drivers/virtual-device.c:387 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.497: Processing command SLEEP 100 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.497: Sleeping 100ms 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.597: Sleeping completed 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.597: 127405285: ../libfprint/drivers/virtual-device.c:387 180s (process:4408): libfprint-device-DEBUG: 03:38:47.597: Device reported open completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.597: Completing action FPI_DEVICE_ACTION_OPEN in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.597: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s (process:4408): libfprint-device-DEBUG: 03:38:47.597: Device reported close completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.597: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.597: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s ok 180s test_verify (__main__.VirtualDeviceBusyDeviceOperations.test_verify) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.597: 127405593: ../libfprint/drivers/virtual-device.c:387 180s (process:4408): libfprint-device-DEBUG: 03:38:47.597: Device reported open completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.597: Completing action FPI_DEVICE_ACTION_OPEN in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.598: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.598: Got a new connection! 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.598: Got instructions of length 9 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.598: Received command SLEEP 200 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.598: Processing command SLEEP 200 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.598: Sleeping 200ms 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.798: Sleeping completed 180s (process:4408): libfprint-device-DEBUG: 03:38:47.798: Device reported close completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.798: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.798: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s ok 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.799: 127606629: ../libfprint/drivers/virtual-device.c:752 180s (process:4408): libfprint-context-DEBUG: 03:38:47.799: Initializing FpContext (libfprint version 1.94.8+tod1) 180s (process:4408): libfprint-tod-DEBUG: 03:38:47.799: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 180s (process:4408): libfprint-context-DEBUG: 03:38:47.802: No driver found for USB device 1D6B:0003 180s (process:4408): libfprint-context-DEBUG: 03:38:47.802: No driver found for USB device 0627:0001 180s (process:4408): libfprint-context-DEBUG: 03:38:47.802: No driver found for USB device 0627:0001 180s (process:4408): libfprint-context-DEBUG: 03:38:47.802: No driver found for USB device 1D6B:0002 180s (process:4408): libfprint-context-DEBUG: 03:38:47.802: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-jyvnjxfo/virtual-device.socket 180s (process:4408): libfprint-context-DEBUG: 03:38:47.802: created 180s (process:4408): libfprint-device-DEBUG: 03:38:47.804: Device reported probe completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.804: Completing action FPI_DEVICE_ACTION_PROBE in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.804: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s test_capture (__main__.VirtualDeviceClosed.test_capture) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.804: 127611904: ../libfprint/drivers/virtual-device.c:387 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.804: 127611922: ../libfprint/drivers/virtual-device-listener.c:153 180s (process:4408): libfprint-device-DEBUG: 03:38:47.804: Device reported open completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.804: Completing action FPI_DEVICE_ACTION_OPEN in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.804: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s (process:4408): libfprint-device-DEBUG: 03:38:47.804: Device reported close completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.804: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.804: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s ok 180s test_close (__main__.VirtualDeviceClosed.test_close) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.804: 127612343: ../libfprint/drivers/virtual-device.c:387 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.804: 127612352: ../libfprint/drivers/virtual-device-listener.c:153 180s (process:4408): libfprint-device-DEBUG: 03:38:47.804: Device reported open completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.804: Completing action FPI_DEVICE_ACTION_OPEN in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.804: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s (process:4408): libfprint-device-DEBUG: 03:38:47.804: Device reported close completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.804: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.804: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s ok 180s test_delete_print (__main__.VirtualDeviceClosed.test_delete_print) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.805: 127612645: ../libfprint/drivers/virtual-device.c:387 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.805: 127612657: ../libfprint/drivers/virtual-device-listener.c:153 180s (process:4408): libfprint-device-DEBUG: 03:38:47.805: Device reported open completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.805: Completing action FPI_DEVICE_ACTION_OPEN in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.805: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s (process:4408): libfprint-device-DEBUG: 03:38:47.805: Device reported close completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.805: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.805: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s ok 180s test_enroll (__main__.VirtualDeviceClosed.test_enroll) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.805: 127612981: ../libfprint/drivers/virtual-device.c:387 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.805: 127612993: ../libfprint/drivers/virtual-device-listener.c:153 180s (process:4408): libfprint-device-DEBUG: 03:38:47.805: Device reported open completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.805: Completing action FPI_DEVICE_ACTION_OPEN in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.805: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s (process:4408): libfprint-device-DEBUG: 03:38:47.805: Device reported close completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.805: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.805: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s ok 180s test_identify (__main__.VirtualDeviceClosed.test_identify) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.805: 127613289: ../libfprint/drivers/virtual-device.c:387 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.805: 127613302: ../libfprint/drivers/virtual-device-listener.c:153 180s (process:4408): libfprint-device-DEBUG: 03:38:47.805: Device reported open completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.805: Completing action FPI_DEVICE_ACTION_OPEN in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.805: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s (process:4408): libfprint-device-DEBUG: 03:38:47.805: Device reported close completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.805: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.805: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s ok 180s test_list_prints (__main__.VirtualDeviceClosed.test_list_prints) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.805: 127613573: ../libfprint/drivers/virtual-device.c:387 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.805: 127613584: ../libfprint/drivers/virtual-device-listener.c:153 180s (process:4408): libfprint-device-DEBUG: 03:38:47.806: Device reported open completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.806: Completing action FPI_DEVICE_ACTION_OPEN in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.806: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s (process:4408): libfprint-device-DEBUG: 03:38:47.806: Device reported close completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.806: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.806: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s ok 180s test_verify (__main__.VirtualDeviceClosed.test_verify) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.806: 127613875: ../libfprint/drivers/virtual-device.c:387 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.806: 127613886: ../libfprint/drivers/virtual-device-listener.c:153 180s (process:4408): libfprint-device-DEBUG: 03:38:47.806: Device reported open completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.806: Completing action FPI_DEVICE_ACTION_OPEN in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.806: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s (process:4408): libfprint-device-DEBUG: 03:38:47.806: Device reported close completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.806: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.806: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s ok 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.806: 127614321: ../libfprint/drivers/virtual-device.c:752 180s (process:4408): libfprint-context-DEBUG: 03:38:47.807: Initializing FpContext (libfprint version 1.94.8+tod1) 180s (process:4408): libfprint-tod-DEBUG: 03:38:47.807: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 180s (process:4408): libfprint-context-DEBUG: 03:38:47.809: No driver found for USB device 1D6B:0003 180s (process:4408): libfprint-context-DEBUG: 03:38:47.809: No driver found for USB device 0627:0001 180s (process:4408): libfprint-context-DEBUG: 03:38:47.809: No driver found for USB device 0627:0001 180s (process:4408): libfprint-context-DEBUG: 03:38:47.809: No driver found for USB device 1D6B:0002 180s (process:4408): libfprint-context-DEBUG: 03:38:47.809: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-jyvnjxfo/virtual-device.socket 180s (process:4408): libfprint-context-DEBUG: 03:38:47.809: created 180s (process:4408): libfprint-context-DEBUG: 03:38:47.809: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-r_zxfgk8/virtual-device-storage.socket 180s (process:4408): libfprint-context-DEBUG: 03:38:47.809: created 180s (process:4408): libfprint-device-DEBUG: 03:38:47.811: Device reported probe completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.811: Device reported probe completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.811: Completing action FPI_DEVICE_ACTION_PROBE in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.811: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s (process:4408): libfprint-device-DEBUG: 03:38:47.811: Completing action FPI_DEVICE_ACTION_PROBE in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.811: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s test_capture_unsupported (__main__.VirtualDeviceStorage.test_capture_unsupported) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.811: 127619247: ../libfprint/drivers/virtual-device.c:387 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.811: 127619257: ../libfprint/drivers/virtual-device-listener.c:153 180s (process:4408): libfprint-device-DEBUG: 03:38:47.811: Device reported open completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.811: Completing action FPI_DEVICE_ACTION_OPEN in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.811: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.811: Got a new connection! 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.811: Got instructions of length 5 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.811: Received command CONT 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.812: Processing command CONT 180s (process:4408): libfprint-device-DEBUG: 03:38:47.812: Device reported deletion completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.812: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.812: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.812: Got a new connection! 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.812: Got instructions of length 16 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.812: Received command SET_KEEP_ALIVE 0 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.812: Keep alive toggled: 0 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.812: Got a new connection! 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.812: Got instructions of length 19 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.812: Received command SET_ENROLL_STAGES 5 180s (process:4408): libfprint-device-DEBUG: 03:38:47.812: Device reported close completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.812: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.812: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s ok 180s test_change_enroll_stages (__main__.VirtualDeviceStorage.test_change_enroll_stages) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.812: 127620238: ../libfprint/drivers/virtual-device.c:387 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.812: 127620250: ../libfprint/drivers/virtual-device-listener.c:153 180s (process:4408): libfprint-device-DEBUG: 03:38:47.812: Device reported open completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.812: Completing action FPI_DEVICE_ACTION_OPEN in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.812: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.812: Got a new connection! 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.812: Got instructions of length 20 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.812: Received command SET_ENROLL_STAGES 20 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.813: Got a new connection! 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.813: Got instructions of length 19 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.813: Received command SET_ENROLL_STAGES 1 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.813: Got a new connection! 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.813: Got instructions of length 19 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.813: Received command SET_ENROLL_STAGES 0 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.813: Got a new connection! 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.813: Got instructions of length 5 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.813: Received command CONT 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.813: Processing command CONT 180s (process:4408): libfprint-device-DEBUG: 03:38:47.813: Device reported deletion completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.813: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.813: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.813: Got a new connection! 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.813: Got instructions of length 16 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.813: Received command SET_KEEP_ALIVE 0 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.813: Keep alive toggled: 0 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.813: Got a new connection! 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.813: Got instructions of length 19 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.813: Received command SET_ENROLL_STAGES 5 180s (process:4408): libfprint-device-DEBUG: 03:38:47.814: Device reported close completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.814: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.814: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s ok 180s test_change_scan_type (__main__.VirtualDeviceStorage.test_change_scan_type) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.814: 127621754: ../libfprint/drivers/virtual-device.c:387 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.814: 127621764: ../libfprint/drivers/virtual-device-listener.c:153 180s (process:4408): libfprint-device-DEBUG: 03:38:47.814: Device reported open completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.814: Completing action FPI_DEVICE_ACTION_OPEN in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.814: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.814: Got a new connection! 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.814: Got instructions of length 19 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.814: Received command SET_SCAN_TYPE press 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.814: Got a new connection! 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.814: Got instructions of length 19 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.814: Received command SET_SCAN_TYPE swipe 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.814: Got a new connection! 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.814: Got instructions of length 25 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.814: Received command SET_SCAN_TYPE eye-contact 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.815: Got a new connection! 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.815: Got instructions of length 5 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.815: Received command CONT 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.815: Processing command CONT 180s (process:4408): libfprint-device-DEBUG: 03:38:47.815: Device reported deletion completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.815: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.815: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.815: Got a new connection! 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.815: Got instructions of length 16 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.815: Received command SET_KEEP_ALIVE 0 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.815: Keep alive toggled: 0 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.815: Got a new connection! 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.815: Got instructions of length 19 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.815: Received command SET_ENROLL_STAGES 5 180s (process:4408): libfprint-device-DEBUG: 03:38:47.815: Device reported close completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.815: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.815: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s ok 180s test_clear_storage (__main__.VirtualDeviceStorage.test_clear_storage) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.815: 127623206: ../libfprint/drivers/virtual-device.c:387 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.815: 127623216: ../libfprint/drivers/virtual-device-listener.c:153 180s (process:4408): libfprint-device-DEBUG: 03:38:47.815: Device reported open completion 180s (process:4408): libfprint-device-DEBUG: 03:38:47.815: Completing action FPI_DEVICE_ACTION_OPEN in idle! 180s (process:4408): libfprint-device-DEBUG: 03:38:47.815: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:47.815: Got a new connection! 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.815: Got instructions of length 9 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.815: Received command INSERT p1 180s (process:4408): libfprint-virtual_device-DEBUG: 03:38:47.815: Processing command INSERT p1 181s (process:4408): libfprint-device-DEBUG: 03:38:48.316: Device reported listing completion 181s (process:4408): libfprint-device-DEBUG: 03:38:48.316: Completing action FPI_DEVICE_ACTION_LIST in idle! 181s (process:4408): libfprint-device-DEBUG: 03:38:48.316: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 181s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:48.316: Got a new connection! 181s (process:4408): libfprint-virtual_device-DEBUG: 03:38:48.316: Got instructions of length 5 181s (process:4408): libfprint-virtual_device-DEBUG: 03:38:48.316: Received command CONT 181s (process:4408): libfprint-virtual_device-DEBUG: 03:38:48.316: Processing command CONT 181s (process:4408): libfprint-device-DEBUG: 03:38:48.317: Device reported deletion completion 181s (process:4408): libfprint-device-DEBUG: 03:38:48.317: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 181s (process:4408): libfprint-device-DEBUG: 03:38:48.317: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 181s (process:4408): libfprint-device-DEBUG: 03:38:48.817: Device reported listing completion 181s (process:4408): libfprint-device-DEBUG: 03:38:48.817: Completing action FPI_DEVICE_ACTION_LIST in idle! 181s (process:4408): libfprint-device-DEBUG: 03:38:48.817: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 181s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:48.818: Got a new connection! 181s (process:4408): libfprint-virtual_device-DEBUG: 03:38:48.818: Got instructions of length 5 181s (process:4408): libfprint-virtual_device-DEBUG: 03:38:48.818: Received command CONT 181s (process:4408): libfprint-virtual_device-DEBUG: 03:38:48.818: Processing command CONT 181s (process:4408): libfprint-device-DEBUG: 03:38:48.818: Device reported deletion completion 181s (process:4408): libfprint-device-DEBUG: 03:38:48.818: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 181s (process:4408): libfprint-device-DEBUG: 03:38:48.818: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 181s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:48.818: Got a new connection! 181s (process:4408): libfprint-virtual_device-DEBUG: 03:38:48.818: Got instructions of length 16 181s (process:4408): libfprint-virtual_device-DEBUG: 03:38:48.818: Received command SET_KEEP_ALIVE 0 181s (process:4408): libfprint-virtual_device-DEBUG: 03:38:48.818: Keep alive toggled: 0 181s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:48.818: Got a new connection! 181s (process:4408): libfprint-virtual_device-DEBUG: 03:38:48.818: Got instructions of length 19 181s (process:4408): libfprint-virtual_device-DEBUG: 03:38:48.818: Received command SET_ENROLL_STAGES 5 181s (process:4408): libfprint-device-DEBUG: 03:38:48.818: Device reported close completion 181s (process:4408): libfprint-device-DEBUG: 03:38:48.818: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 181s (process:4408): libfprint-device-DEBUG: 03:38:48.818: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 181s 181s ok 181s test_clear_storage_error (__main__.VirtualDeviceStorage.test_clear_storage_error) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:48.818: 128626593: ../libfprint/drivers/virtual-device.c:387 181s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:48.818: 128626617: ../libfprint/drivers/virtual-device-listener.c:153 181s (process:4408): libfprint-device-DEBUG: 03:38:48.819: Device reported open completion 181s (process:4408): libfprint-device-DEBUG: 03:38:48.819: Completing action FPI_DEVICE_ACTION_OPEN in idle! 181s (process:4408): libfprint-device-DEBUG: 03:38:48.819: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 181s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:48.819: Got a new connection! 181s (process:4408): libfprint-virtual_device-DEBUG: 03:38:48.819: Got instructions of length 9 181s (process:4408): libfprint-virtual_device-DEBUG: 03:38:48.819: Received command INSERT p1 181s (process:4408): libfprint-virtual_device-DEBUG: 03:38:48.819: Processing command INSERT p1 182s (process:4408): libfprint-device-DEBUG: 03:38:49.320: Device reported listing completion 182s (process:4408): libfprint-device-DEBUG: 03:38:49.320: Completing action FPI_DEVICE_ACTION_LIST in idle! 182s (process:4408): libfprint-device-DEBUG: 03:38:49.320: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 182s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:49.320: Got a new connection! 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.320: Got instructions of length 7 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.320: Received command ERROR 5 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.320: Processing command ERROR 5 182s (process:4408): libfprint-device-DEBUG: 03:38:49.320: Device reported deletion completion 182s (process:4408): libfprint-device-DEBUG: 03:38:49.320: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 182s (process:4408): libfprint-device-DEBUG: 03:38:49.320: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 182s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:49.320: Got a new connection! 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.321: Got instructions of length 5 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.321: Received command CONT 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.321: Processing command CONT 182s (process:4408): libfprint-device-DEBUG: 03:38:49.321: Device reported deletion completion 182s (process:4408): libfprint-device-DEBUG: 03:38:49.321: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 182s (process:4408): libfprint-device-DEBUG: 03:38:49.321: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 182s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:49.321: Got a new connection! 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.321: Got instructions of length 16 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.321: Received command SET_KEEP_ALIVE 0 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.321: Keep alive toggled: 0 182s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:49.321: Got a new connection! 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.321: Got instructions of length 19 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.321: Received command SET_ENROLL_STAGES 5 182s (process:4408): libfprint-device-DEBUG: 03:38:49.321: Device reported close completion 182s (process:4408): libfprint-device-DEBUG: 03:38:49.321: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 182s (process:4408): libfprint-device-DEBUG: 03:38:49.321: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 182s 182s ok 182s test_close_error (__main__.VirtualDeviceStorage.test_close_error) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.321: 129129476: ../libfprint/drivers/virtual-device.c:387 182s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:49.321: 129129500: ../libfprint/drivers/virtual-device-listener.c:153 182s (process:4408): libfprint-device-DEBUG: 03:38:49.321: Device reported open completion 182s (process:4408): libfprint-device-DEBUG: 03:38:49.322: Completing action FPI_DEVICE_ACTION_OPEN in idle! 182s (process:4408): libfprint-device-DEBUG: 03:38:49.322: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 182s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:49.322: Got a new connection! 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.322: Got instructions of length 9 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.322: Received command SLEEP 100 182s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:49.322: Got a new connection! 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.322: Got instructions of length 7 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.322: Received command ERROR 4 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.322: Processing command SLEEP 100 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.322: Sleeping 100ms 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.422: Sleeping completed 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.422: Processing command ERROR 4 182s (process:4408): libfprint-device-DEBUG: 03:38:49.422: Device reported close completion 182s (process:4408): libfprint-device-DEBUG: 03:38:49.422: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 182s (process:4408): libfprint-device-DEBUG: 03:38:49.422: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 182s ok 182s test_close_while_opening (__main__.VirtualDeviceStorage.test_close_while_opening) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.423: 129230767: ../libfprint/drivers/virtual-device.c:387 182s (process:4408): libfprint-device-DEBUG: 03:38:49.423: Device reported open completion 182s (process:4408): libfprint-device-DEBUG: 03:38:49.423: Completing action FPI_DEVICE_ACTION_OPEN in idle! 182s (process:4408): libfprint-device-DEBUG: 03:38:49.423: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 182s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:49.423: Got a new connection! 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.423: Got instructions of length 16 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.423: Received command SET_KEEP_ALIVE 1 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.423: Keep alive toggled: 1 182s (process:4408): libfprint-device-DEBUG: 03:38:49.423: Device reported close completion 182s (process:4408): libfprint-device-DEBUG: 03:38:49.423: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 182s (process:4408): libfprint-device-DEBUG: 03:38:49.423: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 182s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:49.423: Got a new connection! 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.423: Got instructions of length 9 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.423: Received command SLEEP 500 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.423: 129231451: ../libfprint/drivers/virtual-device.c:387 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.423: Processing command SLEEP 500 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.423: Sleeping 500ms 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.924: Sleeping completed 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.924: 129732157: ../libfprint/drivers/virtual-device.c:387 182s (process:4408): libfprint-device-DEBUG: 03:38:49.924: Device reported open completion 182s (process:4408): libfprint-device-DEBUG: 03:38:49.924: Completing action FPI_DEVICE_ACTION_OPEN in idle! 182s (process:4408): libfprint-device-DEBUG: 03:38:49.924: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 182s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:49.924: Got a new connection! 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.924: Got instructions of length 5 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.925: Received command CONT 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.925: Processing command CONT 182s (process:4408): libfprint-device-DEBUG: 03:38:49.925: Device reported deletion completion 182s (process:4408): libfprint-device-DEBUG: 03:38:49.925: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 182s (process:4408): libfprint-device-DEBUG: 03:38:49.925: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 182s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:49.925: Got a new connection! 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.925: Got instructions of length 16 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.925: Received command SET_KEEP_ALIVE 0 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.925: Keep alive toggled: 0 182s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:49.925: Got a new connection! 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.925: Got instructions of length 19 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.925: Received command SET_ENROLL_STAGES 5 182s (process:4408): libfprint-device-DEBUG: 03:38:49.925: Device reported close completion 182s (process:4408): libfprint-device-DEBUG: 03:38:49.925: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 182s (process:4408): libfprint-device-DEBUG: 03:38:49.925: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 182s ok 182s test_delayed_open (__main__.VirtualDeviceStorage.test_delayed_open) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.925: 129733390: ../libfprint/drivers/virtual-device.c:387 182s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:49.925: 129733411: ../libfprint/drivers/virtual-device-listener.c:153 182s (process:4408): libfprint-device-DEBUG: 03:38:49.932: Device reported open completion 182s (process:4408): libfprint-device-DEBUG: 03:38:49.932: Completing action FPI_DEVICE_ACTION_OPEN in idle! 182s (process:4408): libfprint-device-DEBUG: 03:38:49.932: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 182s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:49.933: Got a new connection! 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.933: Got instructions of length 16 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.933: Received command IGNORED_COMMAND 182s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:49.933: Got a new connection! 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.933: Got instructions of length 9 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.933: Received command SLEEP 500 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.933: Processing command IGNORED_COMMAND 182s (process:4408): libfprint-device-DEBUG: 03:38:49.933: Device reported close completion 182s (process:4408): libfprint-device-DEBUG: 03:38:49.933: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 182s (process:4408): libfprint-device-DEBUG: 03:38:49.933: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.933: 129741142: ../libfprint/drivers/virtual-device.c:387 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.933: Processing command SLEEP 500 182s (process:4408): libfprint-virtual_device-DEBUG: 03:38:49.933: Sleeping 500ms 183s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.434: Sleeping completed 183s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.434: 130241867: ../libfprint/drivers/virtual-device.c:387 183s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:50.434: 130241897: ../libfprint/drivers/virtual-device-listener.c:153 183s (process:4408): libfprint-device-DEBUG: 03:38:50.434: Device reported open completion 183s (process:4408): libfprint-device-DEBUG: 03:38:50.434: Completing action FPI_DEVICE_ACTION_OPEN in idle! 183s (process:4408): libfprint-device-DEBUG: 03:38:50.434: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 183s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:50.434: Got a new connection! 183s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.435: Got instructions of length 5 183s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.435: Received command CONT 183s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.435: Processing command CONT 183s (process:4408): libfprint-device-DEBUG: 03:38:50.435: Device reported deletion completion 183s (process:4408): libfprint-device-DEBUG: 03:38:50.435: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 183s (process:4408): libfprint-device-DEBUG: 03:38:50.435: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 183s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:50.435: Got a new connection! 183s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.435: Got instructions of length 16 183s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.435: Received command SET_KEEP_ALIVE 0 183s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.435: Keep alive toggled: 0 183s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:50.435: Got a new connection! 183s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.435: Got instructions of length 19 183s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.435: Received command SET_ENROLL_STAGES 5 183s (process:4408): libfprint-device-DEBUG: 03:38:50.435: Device reported close completion 183s (process:4408): libfprint-device-DEBUG: 03:38:50.435: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 183s (process:4408): libfprint-device-DEBUG: 03:38:50.435: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 183s ok 183s test_delayed_open_with_keep_alive (__main__.VirtualDeviceStorage.test_delayed_open_with_keep_alive) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.436: 130243731: ../libfprint/drivers/virtual-device.c:387 183s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:50.436: 130243753: ../libfprint/drivers/virtual-device-listener.c:153 183s (process:4408): libfprint-device-DEBUG: 03:38:50.436: Device reported open completion 183s (process:4408): libfprint-device-DEBUG: 03:38:50.436: Completing action FPI_DEVICE_ACTION_OPEN in idle! 183s (process:4408): libfprint-device-DEBUG: 03:38:50.436: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 183s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:50.436: Got a new connection! 183s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.436: Got instructions of length 16 183s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.436: Received command SET_KEEP_ALIVE 1 183s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.436: Keep alive toggled: 1 183s (process:4408): libfprint-device-DEBUG: 03:38:50.436: Device reported close completion 183s (process:4408): libfprint-device-DEBUG: 03:38:50.436: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 183s (process:4408): libfprint-device-DEBUG: 03:38:50.436: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 183s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:50.436: Got a new connection! 183s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.436: Got instructions of length 9 183s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.436: Received command SLEEP 500 183s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.436: 130244604: ../libfprint/drivers/virtual-device.c:387 183s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.437: Processing command SLEEP 500 183s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.437: Sleeping 500ms 183s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.937: Sleeping completed 183s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.937: 130745274: ../libfprint/drivers/virtual-device.c:387 183s (process:4408): libfprint-device-DEBUG: 03:38:50.937: Device reported open completion 183s (process:4408): libfprint-device-DEBUG: 03:38:50.937: Completing action FPI_DEVICE_ACTION_OPEN in idle! 183s (process:4408): libfprint-device-DEBUG: 03:38:50.937: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 183s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:50.938: Got a new connection! 183s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.938: Got instructions of length 5 183s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.938: Received command CONT 183s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.938: Processing command CONT 183s (process:4408): libfprint-device-DEBUG: 03:38:50.938: Device reported deletion completion 183s (process:4408): libfprint-device-DEBUG: 03:38:50.938: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 183s (process:4408): libfprint-device-DEBUG: 03:38:50.938: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 183s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:50.938: Got a new connection! 183s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.938: Got instructions of length 16 183s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.938: Received command SET_KEEP_ALIVE 0 183s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.938: Keep alive toggled: 0 183s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:50.938: Got a new connection! 183s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.938: Got instructions of length 19 183s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.938: Received command SET_ENROLL_STAGES 5 183s (process:4408): libfprint-device-DEBUG: 03:38:50.938: Device reported close completion 183s (process:4408): libfprint-device-DEBUG: 03:38:50.938: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 184s (process:4408): libfprint-device-DEBUG: 03:38:50.938: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 184s ok 184s test_delete_error (__main__.VirtualDeviceStorage.test_delete_error) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.938: 130746589: ../libfprint/drivers/virtual-device.c:387 184s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:50.938: 130746611: ../libfprint/drivers/virtual-device-listener.c:153 184s (process:4408): libfprint-device-DEBUG: 03:38:50.939: Device reported open completion 184s (process:4408): libfprint-device-DEBUG: 03:38:50.939: Completing action FPI_DEVICE_ACTION_OPEN in idle! 184s (process:4408): libfprint-device-DEBUG: 03:38:50.939: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 184s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:50.939: Got a new connection! 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.939: Got instructions of length 9 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.939: Received command SLEEP 100 184s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:50.939: Got a new connection! 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.939: Got instructions of length 7 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.939: Received command ERROR 7 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.939: Processing command SLEEP 100 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:50.939: Sleeping 100ms 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:51.039: Sleeping completed 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:51.040: Processing command ERROR 7 184s (process:4408): libfprint-device-DEBUG: 03:38:51.040: Device reported deletion completion 184s (process:4408): libfprint-device-DEBUG: 03:38:51.040: Completing action FPI_DEVICE_ACTION_DELETE in idle! 184s (process:4408): libfprint-device-DEBUG: 03:38:51.040: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 184s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:51.040: Got a new connection! 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:51.040: Got instructions of length 5 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:51.040: Received command CONT 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:51.040: Processing command CONT 184s (process:4408): libfprint-device-DEBUG: 03:38:51.040: Device reported deletion completion 184s (process:4408): libfprint-device-DEBUG: 03:38:51.040: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 184s (process:4408): libfprint-device-DEBUG: 03:38:51.040: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 184s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:51.040: Got a new connection! 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:51.041: Got instructions of length 16 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:51.041: Received command SET_KEEP_ALIVE 0 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:51.041: Keep alive toggled: 0 184s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:51.041: Got a new connection! 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:51.041: Got instructions of length 19 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:51.041: Received command SET_ENROLL_STAGES 5 184s (process:4408): libfprint-device-DEBUG: 03:38:51.041: Device reported close completion 184s (process:4408): libfprint-device-DEBUG: 03:38:51.041: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 184s (process:4408): libfprint-device-DEBUG: 03:38:51.041: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 184s ok 184s test_delete_multiple_times (__main__.VirtualDeviceStorage.test_delete_multiple_times) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:51.041: 130849161: ../libfprint/drivers/virtual-device.c:387 184s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:51.041: 130849185: ../libfprint/drivers/virtual-device-listener.c:153 184s (process:4408): libfprint-device-DEBUG: 03:38:51.041: Device reported open completion 184s (process:4408): libfprint-device-DEBUG: 03:38:51.041: Completing action FPI_DEVICE_ACTION_OPEN in idle! 184s (process:4408): libfprint-device-DEBUG: 03:38:51.041: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 184s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:51.041: Got a new connection! 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:51.041: Got instructions of length 16 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:51.041: Received command SCAN right-thumb 184s (process:4408): libfprint-device-DEBUG: 03:38:51.042: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:51.042: Processing command SCAN right-thumb 184s (process:4408): libfprint-device-DEBUG: 03:38:51.042: Device reported finger status change: FP_FINGER_STATUS_NEEDED 184s (process:4408): libfprint-device-DEBUG: 03:38:51.042: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 184s (process:4408): libfprint-device-DEBUG: 03:38:51.042: Device reported finger status change: FP_FINGER_STATUS_NEEDED 184s (process:4408): libfprint-device-DEBUG: 03:38:51.042: Device reported enroll progress, reported 1 of 5 have been completed 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:51.042: Sleeping completed 184s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:51.042: Got a new connection! 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:51.042: Got instructions of length 16 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:51.042: Received command SCAN right-thumb 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:51.042: Processing command SCAN right-thumb 184s (process:4408): libfprint-device-DEBUG: 03:38:51.042: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 184s (process:4408): libfprint-device-DEBUG: 03:38:51.042: Device reported finger status change: FP_FINGER_STATUS_NEEDED 184s (process:4408): libfprint-device-DEBUG: 03:38:51.042: Device reported enroll progress, reported 2 of 5 have been completed 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:51.042: Sleeping completed 184s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:51.042: Got a new connection! 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:51.042: Got instructions of length 16 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:51.042: Received command SCAN right-thumb 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:51.042: Processing command SCAN right-thumb 184s (process:4408): libfprint-device-DEBUG: 03:38:51.042: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 184s (process:4408): libfprint-device-DEBUG: 03:38:51.042: Device reported finger status change: FP_FINGER_STATUS_NEEDED 184s (process:4408): libfprint-device-DEBUG: 03:38:51.042: Device reported enroll progress, reported 3 of 5 have been completed 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:51.042: Sleeping completed 184s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:51.043: Got a new connection! 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:51.043: Got instructions of length 16 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:51.043: Received command SCAN right-thumb 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:51.043: Processing command SCAN right-thumb 184s (process:4408): libfprint-device-DEBUG: 03:38:51.043: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 184s (process:4408): libfprint-device-DEBUG: 03:38:51.043: Device reported finger status change: FP_FINGER_STATUS_NEEDED 184s (process:4408): libfprint-device-DEBUG: 03:38:51.043: Device reported enroll progress, reported 4 of 5 have been completed 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:51.043: Sleeping completed 184s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:51.043: Got a new connection! 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:51.043: Got instructions of length 16 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:51.043: Received command SCAN right-thumb 184s (process:4408): libfprint-virtual_device-DEBUG: 03:38:51.043: Processing command SCAN right-thumb 184s (process:4408): libfprint-device-DEBUG: 03:38:51.043: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 184s (process:4408): libfprint-device-DEBUG: 03:38:51.043: Device reported finger status change: FP_FINGER_STATUS_NEEDED 184s (process:4408): libfprint-device-DEBUG: 03:38:51.043: Device reported enroll progress, reported 5 of 5 have been completed 184s (process:4408): libfprint-device-DEBUG: 03:38:51.043: Device reported enroll completion 184s (process:4408): libfprint-device-DEBUG: 03:38:51.043: Device reported finger status change: FP_FINGER_STATUS_NONE 184s (process:4408): libfprint-device-DEBUG: 03:38:51.043: Print for finger FP_FINGER_RIGHT_THUMB enrolled 184s (process:4408): libfprint-device-DEBUG: 03:38:51.043: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 184s (process:4408): libfprint-device-DEBUG: 03:38:51.043: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 184s Executing: libfprint-2/virtual-device.test 184s (process:4408): libfprint-virtual_device_storage-DEBUG: 03:38:51.544: Deleting print right-thumb for user testuser 184s (process:4408): libfprint-device-DEBUG: 03:38:51.544: Device reported deletion completion 184s (process:4408): libfprint-device-DEBUG: 03:38:51.544: Completing action FPI_DEVICE_ACTION_DELETE in idle! 184s (process:4408): libfprint-device-DEBUG: 03:38:51.544: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 185s (process:4408): libfprint-virtual_device_storage-DEBUG: 03:38:52.045: Deleting print right-thumb for user testuser 185s (process:4408): libfprint-device-DEBUG: 03:38:52.045: Device reported deletion completion 185s (process:4408): libfprint-device-DEBUG: 03:38:52.045: Completing action FPI_DEVICE_ACTION_DELETE in idle! 185s (process:4408): libfprint-device-DEBUG: 03:38:52.045: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 185s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:52.046: Got a new connection! 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.046: Got instructions of length 5 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.046: Received command CONT 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.046: Processing command CONT 185s (process:4408): libfprint-device-DEBUG: 03:38:52.046: Device reported deletion completion 185s (process:4408): libfprint-device-DEBUG: 03:38:52.046: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 185s (process:4408): libfprint-device-DEBUG: 03:38:52.046: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 185s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:52.046: Got a new connection! 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.046: Got instructions of length 16 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.046: Received command SET_KEEP_ALIVE 0 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.046: Keep alive toggled: 0 185s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:52.046: Got a new connection! 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.046: Got instructions of length 19 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.046: Received command SET_ENROLL_STAGES 5 185s (process:4408): libfprint-device-DEBUG: 03:38:52.046: Device reported close completion 185s (process:4408): libfprint-device-DEBUG: 03:38:52.046: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 185s (process:4408): libfprint-device-DEBUG: 03:38:52.046: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 185s Enroll done 185s ok 185s test_device_features (__main__.VirtualDeviceStorage.test_device_features) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.046: 131854304: ../libfprint/drivers/virtual-device.c:387 185s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:52.046: 131854314: ../libfprint/drivers/virtual-device-listener.c:153 185s (process:4408): libfprint-device-DEBUG: 03:38:52.046: Device reported open completion 185s (process:4408): libfprint-device-DEBUG: 03:38:52.046: Completing action FPI_DEVICE_ACTION_OPEN in idle! 185s (process:4408): libfprint-device-DEBUG: 03:38:52.046: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 185s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:52.046: Got a new connection! 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.046: Got instructions of length 5 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.046: Received command CONT 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.047: Processing command CONT 185s (process:4408): libfprint-device-DEBUG: 03:38:52.047: Device reported deletion completion 185s (process:4408): libfprint-device-DEBUG: 03:38:52.047: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 185s (process:4408): libfprint-device-DEBUG: 03:38:52.047: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 185s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:52.047: Got a new connection! 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.047: Got instructions of length 16 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.047: Received command SET_KEEP_ALIVE 0 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.047: Keep alive toggled: 0 185s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:52.047: Got a new connection! 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.047: Got instructions of length 19 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.047: Received command SET_ENROLL_STAGES 5 185s (process:4408): libfprint-device-DEBUG: 03:38:52.047: Device reported close completion 185s (process:4408): libfprint-device-DEBUG: 03:38:52.047: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 185s (process:4408): libfprint-device-DEBUG: 03:38:52.047: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 185s ok 185s test_device_properties (__main__.VirtualDeviceStorage.test_device_properties) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.047: 131855087: ../libfprint/drivers/virtual-device.c:387 185s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:52.047: 131855095: ../libfprint/drivers/virtual-device-listener.c:153 185s (process:4408): libfprint-device-DEBUG: 03:38:52.047: Device reported open completion 185s (process:4408): libfprint-device-DEBUG: 03:38:52.047: Completing action FPI_DEVICE_ACTION_OPEN in idle! 185s (process:4408): libfprint-device-DEBUG: 03:38:52.047: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 185s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:52.047: Got a new connection! 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.047: Got instructions of length 5 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.047: Received command CONT 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.047: Processing command CONT 185s (process:4408): libfprint-device-DEBUG: 03:38:52.047: Device reported deletion completion 185s (process:4408): libfprint-device-DEBUG: 03:38:52.047: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 185s (process:4408): libfprint-device-DEBUG: 03:38:52.047: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 185s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:52.047: Got a new connection! 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.047: Got instructions of length 16 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.047: Received command SET_KEEP_ALIVE 0 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.047: Keep alive toggled: 0 185s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:52.048: Got a new connection! 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.048: Got instructions of length 19 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.048: Received command SET_ENROLL_STAGES 5 185s (process:4408): libfprint-device-DEBUG: 03:38:52.048: Device reported close completion 185s (process:4408): libfprint-device-DEBUG: 03:38:52.048: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 185s (process:4408): libfprint-device-DEBUG: 03:38:52.048: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 185s ok 185s test_device_sleep (__main__.VirtualDeviceStorage.test_device_sleep) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.048: 131855839: ../libfprint/drivers/virtual-device.c:387 185s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:52.048: 131855847: ../libfprint/drivers/virtual-device-listener.c:153 185s (process:4408): libfprint-device-DEBUG: 03:38:52.048: Device reported open completion 185s (process:4408): libfprint-device-DEBUG: 03:38:52.048: Completing action FPI_DEVICE_ACTION_OPEN in idle! 185s (process:4408): libfprint-device-DEBUG: 03:38:52.048: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 185s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:52.048: Got a new connection! 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.048: Got instructions of length 10 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.048: Received command SLEEP 1500 185s (process:4408): libfprint-device-DEBUG: 03:38:52.049: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.049: Processing command SLEEP 1500 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.049: Sleeping 1500ms 185s (process:4408): libfprint-device-DEBUG: 03:38:52.349: Idle cancelling on ongoing operation! 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.349: Got cancellation! 185s (process:4408): libfprint-device-DEBUG: 03:38:52.349: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:4408): libfprint-device-DEBUG: 03:38:52.349: Device reported identify completion 185s (process:4408): libfprint-device-DEBUG: 03:38:52.349: Device reported finger status change: FP_FINGER_STATUS_NONE 185s (process:4408): libfprint-device-DEBUG: 03:38:52.349: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 185s (process:4408): libfprint-device-DEBUG: 03:38:52.349: Updated temperature model after 0.30 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 185s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:52.549: Got a new connection! 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.549: Got instructions of length 5 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.549: Received command CONT 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.550: Processing command CONT 185s (process:4408): libfprint-device-DEBUG: 03:38:52.550: Device reported deletion completion 185s (process:4408): libfprint-device-DEBUG: 03:38:52.550: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 185s (process:4408): libfprint-device-DEBUG: 03:38:52.550: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 185s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:52.550: Got a new connection! 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.550: Got instructions of length 16 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.550: Received command SET_KEEP_ALIVE 0 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.550: Keep alive toggled: 0 185s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:52.550: Got a new connection! 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.550: Got instructions of length 19 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.550: Received command SET_ENROLL_STAGES 5 185s (process:4408): libfprint-device-DEBUG: 03:38:52.550: Device reported close completion 185s (process:4408): libfprint-device-DEBUG: 03:38:52.551: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 185s (process:4408): libfprint-device-DEBUG: 03:38:52.551: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 185s ok 185s test_device_sleep_before_completing_verify (__main__.VirtualDeviceStorage.test_device_sleep_before_completing_verify) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.551: 132358922: ../libfprint/drivers/virtual-device.c:387 185s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:52.551: 132358967: ../libfprint/drivers/virtual-device-listener.c:153 185s (process:4408): libfprint-device-DEBUG: 03:38:52.551: Device reported open completion 185s (process:4408): libfprint-device-DEBUG: 03:38:52.551: Completing action FPI_DEVICE_ACTION_OPEN in idle! 185s (process:4408): libfprint-device-DEBUG: 03:38:52.551: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 185s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:52.551: Got a new connection! 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.551: Got instructions of length 14 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.551: Received command SCAN foo-print 185s (process:4408): libfprint-device-DEBUG: 03:38:52.551: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.552: Processing command SCAN foo-print 185s (process:4408): libfprint-device-DEBUG: 03:38:52.552: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:4408): libfprint-device-DEBUG: 03:38:52.552: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 185s (process:4408): libfprint-device-DEBUG: 03:38:52.552: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:4408): libfprint-device-DEBUG: 03:38:52.552: Device reported enroll progress, reported 1 of 5 have been completed 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.552: Sleeping completed 185s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:52.552: Got a new connection! 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.552: Got instructions of length 14 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.552: Received command SCAN foo-print 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.552: Processing command SCAN foo-print 185s (process:4408): libfprint-device-DEBUG: 03:38:52.552: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 185s (process:4408): libfprint-device-DEBUG: 03:38:52.552: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:4408): libfprint-device-DEBUG: 03:38:52.552: Device reported enroll progress, reported 2 of 5 have been completed 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.552: Sleeping completed 185s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:52.552: Got a new connection! 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.553: Got instructions of length 14 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.553: Received command SCAN foo-print 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.553: Processing command SCAN foo-print 185s (process:4408): libfprint-device-DEBUG: 03:38:52.553: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 185s (process:4408): libfprint-device-DEBUG: 03:38:52.553: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:4408): libfprint-device-DEBUG: 03:38:52.553: Device reported enroll progress, reported 3 of 5 have been completed 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.553: Sleeping completed 185s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:52.553: Got a new connection! 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.553: Got instructions of length 14 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.553: Received command SCAN foo-print 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.553: Processing command SCAN foo-print 185s (process:4408): libfprint-device-DEBUG: 03:38:52.553: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 185s (process:4408): libfprint-device-DEBUG: 03:38:52.553: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:4408): libfprint-device-DEBUG: 03:38:52.553: Device reported enroll progress, reported 4 of 5 have been completed 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.553: Sleeping completed 185s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:52.554: Got a new connection! 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.554: Got instructions of length 14 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.554: Received command SCAN foo-print 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.554: Processing command SCAN foo-print 185s (process:4408): libfprint-device-DEBUG: 03:38:52.554: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 185s (process:4408): libfprint-device-DEBUG: 03:38:52.554: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:4408): libfprint-device-DEBUG: 03:38:52.554: Device reported enroll progress, reported 5 of 5 have been completed 185s (process:4408): libfprint-device-DEBUG: 03:38:52.554: Device reported enroll completion 185s (process:4408): libfprint-device-DEBUG: 03:38:52.554: Device reported finger status change: FP_FINGER_STATUS_NONE 185s (process:4408): libfprint-device-DEBUG: 03:38:52.554: Print for finger FP_FINGER_LEFT_RING enrolled 185s (process:4408): libfprint-device-DEBUG: 03:38:52.554: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 185s (process:4408): libfprint-device-DEBUG: 03:38:52.554: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 185s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:52.554: Got a new connection! 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.554: Got instructions of length 9 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.554: Received command SLEEP 100 185s (process:4408): libfprint-device-DEBUG: 03:38:52.554: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.555: Processing command SLEEP 100 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.555: Sleeping 100ms 185s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:52.555: Got a new connection! 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.555: Got instructions of length 14 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.555: Received command SCAN bar-print 185s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:52.555: Got a new connection! 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.555: Got instructions of length 9 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.555: Received command SLEEP 800 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.655: Sleeping completed 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.655: Processing command SCAN bar-print 185s (process:4408): libfprint-device-DEBUG: 03:38:52.655: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:4408): libfprint-device-DEBUG: 03:38:52.655: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 185s (process:4408): libfprint-virtual_device_storage-DEBUG: 03:38:52.655: Trying to identify print 'bar-print' against a gallery of 1 prints 185s (process:4408): libfprint-device-DEBUG: 03:38:52.655: Device reported identify result 185s (process:4408): libfprint-device-DEBUG: 03:38:52.655: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.655: Processing command SLEEP 800 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.655: Sleeping 800ms 185s (process:4408): libfprint-virtual_device-DEBUG: 03:38:52.655: Sleeping now, command queued for later: SCAN bar-print 185s (process:4408): libfprint-device-DEBUG: 03:38:52.891: Updated temperature model after 0.34 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 186s (process:4408): libfprint-virtual_device-DEBUG: 03:38:53.456: Sleeping completed 186s (process:4408): libfprint-virtual_device-DEBUG: 03:38:53.456: Processing command SCAN bar-print 186s (process:4408): libfprint-device-DEBUG: 03:38:53.456: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 186s (process:4408): libfprint-virtual_device_storage-DEBUG: 03:38:53.456: Trying to identify print 'bar-print' against a gallery of 1 prints 186s (process:4408): libfprint-device-DEBUG: 03:38:53.456: Device reported finger status change: FP_FINGER_STATUS_NEEDED 186s (process:4408): libfprint-device-DEBUG: 03:38:53.456: Device reported identify completion 186s (process:4408): libfprint-device-DEBUG: 03:38:53.456: Device reported finger status change: FP_FINGER_STATUS_NONE 186s (process:4408): libfprint-device-DEBUG: 03:38:53.456: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 186s (process:4408): libfprint-device-DEBUG: 03:38:53.456: Updated temperature model after 0.57 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 186s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:53.457: Got a new connection! 186s (process:4408): libfprint-virtual_device-DEBUG: 03:38:53.457: Got instructions of length 5 186s (process:4408): libfprint-virtual_device-DEBUG: 03:38:53.457: Received command CONT 186s (process:4408): libfprint-virtual_device-DEBUG: 03:38:53.457: Processing command CONT 186s (process:4408): libfprint-device-DEBUG: 03:38:53.457: Device reported deletion completion 186s (process:4408): libfprint-device-DEBUG: 03:38:53.457: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 186s (process:4408): libfprint-device-DEBUG: 03:38:53.457: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 186s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:53.457: Got a new connection! 186s (process:4408): libfprint-virtual_device-DEBUG: 03:38:53.457: Got instructions of length 16 186s (process:4408): libfprint-virtual_device-DEBUG: 03:38:53.457: Received command SET_KEEP_ALIVE 0 186s (process:4408): libfprint-virtual_device-DEBUG: 03:38:53.457: Keep alive toggled: 0 186s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:53.457: Got a new connection! 186s (process:4408): libfprint-virtual_device-DEBUG: 03:38:53.457: Got instructions of length 19 186s (process:4408): libfprint-virtual_device-DEBUG: 03:38:53.457: Received command SET_ENROLL_STAGES 5 186s (process:4408): libfprint-device-DEBUG: 03:38:53.457: Device reported close completion 186s (process:4408): libfprint-device-DEBUG: 03:38:53.457: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 186s (process:4408): libfprint-device-DEBUG: 03:38:53.457: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 186s Enroll done 186s ok 186s test_device_sleep_on_cancellation (__main__.VirtualDeviceStorage.test_device_sleep_on_cancellation) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:53.457: 133265443: ../libfprint/drivers/virtual-device.c:387 186s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:53.457: 133265453: ../libfprint/drivers/virtual-device-listener.c:153 186s (process:4408): libfprint-device-DEBUG: 03:38:53.457: Device reported open completion 186s (process:4408): libfprint-device-DEBUG: 03:38:53.457: Completing action FPI_DEVICE_ACTION_OPEN in idle! 186s (process:4408): libfprint-device-DEBUG: 03:38:53.457: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 186s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:53.458: Got a new connection! 186s (process:4408): libfprint-virtual_device-DEBUG: 03:38:53.458: Got instructions of length 26 186s (process:4408): libfprint-virtual_device-DEBUG: 03:38:53.458: Received command SET_CANCELLATION_ENABLED 0 186s (process:4408): libfprint-virtual_device-DEBUG: 03:38:53.458: Cancellation support toggled: 0 186s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:53.458: Got a new connection! 186s (process:4408): libfprint-virtual_device-DEBUG: 03:38:53.458: Got instructions of length 10 186s (process:4408): libfprint-virtual_device-DEBUG: 03:38:53.458: Received command SLEEP 1500 186s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:53.458: Got a new connection! 186s (process:4408): libfprint-virtual_device-DEBUG: 03:38:53.458: Got instructions of length 14 186s (process:4408): libfprint-virtual_device-DEBUG: 03:38:53.458: Received command SCAN foo-print 186s (process:4408): libfprint-device-DEBUG: 03:38:53.458: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 186s (process:4408): libfprint-virtual_device-DEBUG: 03:38:53.458: Processing command SLEEP 1500 186s (process:4408): libfprint-virtual_device-DEBUG: 03:38:53.458: Sleeping 1500ms 186s (process:4408): libfprint-device-DEBUG: 03:38:53.758: Idle cancelling on ongoing operation! 187s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.959: Sleeping completed 187s (process:4408): libfprint-device-DEBUG: 03:38:54.959: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:4408): libfprint-device-DEBUG: 03:38:54.959: Device reported identify completion 187s (process:4408): libfprint-device-DEBUG: 03:38:54.960: Device reported finger status change: FP_FINGER_STATUS_NONE 187s (process:4408): libfprint-device-DEBUG: 03:38:54.960: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 187s (process:4408): libfprint-device-DEBUG: 03:38:54.960: Updated temperature model after 1.50 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 187s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.960: Processing command SCAN foo-print 187s (process:4408): libfprint-device-DEBUG: 03:38:54.960: Device reported close completion 187s (process:4408): libfprint-device-DEBUG: 03:38:54.960: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 187s (process:4408): libfprint-device-DEBUG: 03:38:54.961: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s ok 188s test_duplicate_enroll (__main__.VirtualDeviceStorage.test_duplicate_enroll) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.961: 134769350: ../libfprint/drivers/virtual-device.c:387 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.961: 134769402: ../libfprint/drivers/virtual-device-listener.c:153 188s (process:4408): libfprint-device-DEBUG: 03:38:54.961: Device reported open completion 188s (process:4408): libfprint-device-DEBUG: 03:38:54.962: Completing action FPI_DEVICE_ACTION_OPEN in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:54.962: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.962: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.962: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.962: Received command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:54.962: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.962: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:54.962: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:54.962: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:54.962: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:54.962: Device reported enroll progress, reported 1 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.962: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.963: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.963: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.963: Received command SCAN testprint 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.963: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:54.963: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:54.963: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:54.963: Device reported enroll progress, reported 2 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.963: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.963: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.963: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.963: Received command SCAN testprint 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.963: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:54.963: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:54.963: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:54.963: Device reported enroll progress, reported 3 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.963: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.963: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.963: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.963: Received command SCAN testprint 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.963: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:54.963: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:54.963: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:54.963: Device reported enroll progress, reported 4 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.963: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.964: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.964: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.964: Received command SCAN testprint 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.964: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:54.964: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:54.964: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:54.964: Device reported enroll progress, reported 5 of 5 have been completed 188s (process:4408): libfprint-device-DEBUG: 03:38:54.964: Device reported enroll completion 188s (process:4408): libfprint-device-DEBUG: 03:38:54.964: Device reported finger status change: FP_FINGER_STATUS_NONE 188s (process:4408): libfprint-device-DEBUG: 03:38:54.964: Print for finger FP_FINGER_LEFT_LITTLE enrolled 188s (process:4408): libfprint-device-DEBUG: 03:38:54.964: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:54.964: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.965: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.965: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.965: Received command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:54.965: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.965: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:54.965: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:54.965: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:54.965: Device reported enroll completion 188s (process:4408): libfprint-device-DEBUG: 03:38:54.965: Device reported finger status change: FP_FINGER_STATUS_NONE 188s (process:4408): libfprint-device-DEBUG: 03:38:54.965: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:54.965: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.965: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.965: Got instructions of length 5 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.965: Received command CONT 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.965: Processing command CONT 188s (process:4408): libfprint-device-DEBUG: 03:38:54.965: Device reported deletion completion 188s (process:4408): libfprint-device-DEBUG: 03:38:54.965: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:54.965: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.965: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.965: Got instructions of length 16 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.965: Received command SET_KEEP_ALIVE 0 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.966: Keep alive toggled: 0 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.966: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.966: Got instructions of length 19 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.966: Received command SET_ENROLL_STAGES 5 188s (process:4408): libfprint-device-DEBUG: 03:38:54.966: Device reported close completion 188s (process:4408): libfprint-device-DEBUG: 03:38:54.966: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:54.966: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s Enroll done 188s Enroll done 188s ok 188s test_enroll (__main__.VirtualDeviceStorage.test_enroll) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.966: 134774135: ../libfprint/drivers/virtual-device.c:387 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.966: 134774161: ../libfprint/drivers/virtual-device-listener.c:153 188s (process:4408): libfprint-device-DEBUG: 03:38:54.966: Device reported open completion 188s (process:4408): libfprint-device-DEBUG: 03:38:54.966: Completing action FPI_DEVICE_ACTION_OPEN in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:54.966: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.966: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.966: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.966: Received command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:54.967: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.967: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:54.967: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:54.967: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:54.967: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:54.967: Device reported enroll progress, reported 1 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.967: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.967: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.967: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.967: Received command SCAN testprint 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.967: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:54.967: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:54.967: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:54.967: Device reported enroll progress, reported 2 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.967: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.967: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.967: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.967: Received command SCAN testprint 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.967: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:54.967: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:54.967: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:54.967: Device reported enroll progress, reported 3 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.967: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.968: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.968: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.968: Received command SCAN testprint 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.968: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:54.968: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:54.968: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:54.968: Device reported enroll progress, reported 4 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.968: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.968: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.968: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.968: Received command SCAN testprint 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.968: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:54.968: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:54.968: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:54.968: Device reported enroll progress, reported 5 of 5 have been completed 188s (process:4408): libfprint-device-DEBUG: 03:38:54.968: Device reported enroll completion 188s (process:4408): libfprint-device-DEBUG: 03:38:54.968: Device reported finger status change: FP_FINGER_STATUS_NONE 188s (process:4408): libfprint-device-DEBUG: 03:38:54.968: Print for finger FP_FINGER_LEFT_LITTLE enrolled 188s (process:4408): libfprint-device-DEBUG: 03:38:54.968: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:54.968: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.968: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.969: Got instructions of length 5 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.969: Received command CONT 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.969: Processing command CONT 188s (process:4408): libfprint-device-DEBUG: 03:38:54.969: Device reported deletion completion 188s (process:4408): libfprint-device-DEBUG: 03:38:54.969: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:54.969: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.969: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.969: Got instructions of length 16 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.969: Received command SET_KEEP_ALIVE 0 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.969: Keep alive toggled: 0 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.969: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.969: Got instructions of length 19 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.969: Received command SET_ENROLL_STAGES 5 188s (process:4408): libfprint-device-DEBUG: 03:38:54.969: Device reported close completion 188s (process:4408): libfprint-device-DEBUG: 03:38:54.969: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:54.969: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s Enroll done 188s ok 188s test_enroll_script (__main__.VirtualDeviceStorage.test_enroll_script) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.969: 134777483: ../libfprint/drivers/virtual-device.c:387 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.969: 134777505: ../libfprint/drivers/virtual-device-listener.c:153 188s (process:4408): libfprint-device-DEBUG: 03:38:54.969: Device reported open completion 188s (process:4408): libfprint-device-DEBUG: 03:38:54.970: Completing action FPI_DEVICE_ACTION_OPEN in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:54.970: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.970: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.970: Got instructions of length 19 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.970: Received command SET_ENROLL_STAGES 8 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.970: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.970: Got instructions of length 13 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.970: Received command SCAN print-id 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.970: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.970: Got instructions of length 13 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.970: Received command SCAN print-id 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.970: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.970: Got instructions of length 7 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.970: Received command RETRY 1 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.970: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.970: Got instructions of length 13 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.971: Received command SCAN print-id 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.971: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.971: Got instructions of length 7 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.971: Received command RETRY 3 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.971: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.971: Got instructions of length 13 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.971: Received command SCAN print-id 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.971: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.971: Got instructions of length 7 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.971: Received command RETRY 2 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.971: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.971: Got instructions of length 13 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.971: Received command SCAN print-id 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.971: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.971: Got instructions of length 8 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.971: Received command SLEEP 10 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.972: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.972: Got instructions of length 8 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.972: Received command SLEEP 20 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.972: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.972: Got instructions of length 7 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.972: Received command RETRY 0 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.972: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.972: Got instructions of length 7 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.972: Received command RETRY 3 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.972: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.972: Got instructions of length 13 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.972: Received command SCAN print-id 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.972: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.972: Got instructions of length 15 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.972: Received command SCAN another-id 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.973: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.973: Got instructions of length 13 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.973: Received command SCAN print-id 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:54.973: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.973: Got instructions of length 13 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.973: Received command SCAN print-id 188s (process:4408): libfprint-device-DEBUG: 03:38:54.973: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.973: Processing command SCAN print-id 188s (process:4408): libfprint-device-DEBUG: 03:38:54.973: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:54.973: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:54.973: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:54.973: Device reported enroll progress, reported 1 of 8 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.973: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.973: Processing command SCAN print-id 188s (process:4408): libfprint-device-DEBUG: 03:38:54.973: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:54.973: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:54.973: Device reported enroll progress, reported 2 of 8 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.973: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.973: Processing command RETRY 1 188s (process:4408): libfprint-device-DEBUG: 03:38:54.973: Device reported enroll progress, reported 2 of 8 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.973: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.973: Processing command SCAN print-id 188s (process:4408): libfprint-device-DEBUG: 03:38:54.973: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:54.973: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:54.973: Device reported enroll progress, reported 3 of 8 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.973: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.973: Processing command RETRY 3 188s (process:4408): libfprint-device-DEBUG: 03:38:54.973: Device reported enroll progress, reported 3 of 8 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.973: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.973: Processing command SCAN print-id 188s (process:4408): libfprint-device-DEBUG: 03:38:54.973: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:54.973: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:54.973: Device reported enroll progress, reported 4 of 8 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.973: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.974: Processing command RETRY 2 188s (process:4408): libfprint-device-DEBUG: 03:38:54.974: Device reported enroll progress, reported 4 of 8 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.974: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.974: Processing command SCAN print-id 188s (process:4408): libfprint-device-DEBUG: 03:38:54.974: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:54.974: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:54.974: Device reported enroll progress, reported 5 of 8 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.974: Processing command SLEEP 10 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.974: Sleeping 10ms 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.984: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.984: Processing command SLEEP 20 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:54.984: Sleeping 20ms 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.004: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.004: Processing command RETRY 0 188s (process:4408): libfprint-device-DEBUG: 03:38:55.004: Device reported enroll progress, reported 5 of 8 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.004: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.004: Processing command RETRY 3 188s (process:4408): libfprint-device-DEBUG: 03:38:55.004: Device reported enroll progress, reported 5 of 8 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.004: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.004: Processing command SCAN print-id 188s (process:4408): libfprint-device-DEBUG: 03:38:55.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.004: Device reported enroll progress, reported 6 of 8 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.004: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.004: Processing command SCAN another-id 188s (process:4408): libfprint-device-DEBUG: 03:38:55.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.004: Device reported enroll progress, reported 6 of 8 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.004: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.004: Processing command SCAN print-id 188s (process:4408): libfprint-device-DEBUG: 03:38:55.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.004: Device reported enroll progress, reported 7 of 8 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.004: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.004: Processing command SCAN print-id 188s (process:4408): libfprint-device-DEBUG: 03:38:55.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.004: Device reported enroll progress, reported 8 of 8 have been completed 188s (process:4408): libfprint-device-DEBUG: 03:38:55.004: Device reported enroll completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.004: Device reported finger status change: FP_FINGER_STATUS_NONE 188s (process:4408): libfprint-device-DEBUG: 03:38:55.004: Print for finger FP_FINGER_UNKNOWN enrolled 188s (process:4408): libfprint-device-DEBUG: 03:38:55.004: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.004: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.005: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.005: Got instructions of length 5 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.005: Received command CONT 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.005: Processing command CONT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.005: Device reported deletion completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.005: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.005: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.005: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.005: Got instructions of length 16 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.005: Received command SET_KEEP_ALIVE 0 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.005: Keep alive toggled: 0 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.005: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.005: Got instructions of length 19 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.005: Received command SET_ENROLL_STAGES 5 188s (process:4408): libfprint-device-DEBUG: 03:38:55.005: Device reported close completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.005: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.005: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s ok 188s test_enroll_script_interactive (__main__.VirtualDeviceStorage.test_enroll_script_interactive) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.005: 134813391: ../libfprint/drivers/virtual-device.c:387 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.005: 134813401: ../libfprint/drivers/virtual-device-listener.c:153 188s (process:4408): libfprint-device-DEBUG: 03:38:55.005: Device reported open completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.005: Completing action FPI_DEVICE_ACTION_OPEN in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.005: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.006: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.006: Got instructions of length 8 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.006: Received command SLEEP 50 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.006: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.006: Got instructions of length 13 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.006: Received command SCAN print-id 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.006: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.006: Got instructions of length 13 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.006: Received command SCAN print-id 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.006: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.006: Got instructions of length 7 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.006: Received command RETRY 1 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.006: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.006: Got instructions of length 13 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.006: Received command SCAN print-id 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.006: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.006: Got instructions of length 8 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.006: Received command SLEEP 50 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.006: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.006: Got instructions of length 13 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.006: Received command SCAN print-id 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.007: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.007: Got instructions of length 7 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.007: Received command RETRY 2 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.007: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.007: Got instructions of length 15 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.007: Received command SCAN another-id 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.007: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.007: Got instructions of length 13 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.007: Received command SCAN print-id 188s (process:4408): libfprint-device-DEBUG: 03:38:55.007: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.007: Processing command SLEEP 50 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.007: Sleeping 50ms 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.057: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.057: Processing command SCAN print-id 188s (process:4408): libfprint-device-DEBUG: 03:38:55.057: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.057: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.057: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.057: Device reported enroll progress, reported 1 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.057: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.058: Processing command SCAN print-id 188s (process:4408): libfprint-device-DEBUG: 03:38:55.058: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.058: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.058: Device reported enroll progress, reported 2 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.058: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.058: Processing command RETRY 1 188s (process:4408): libfprint-device-DEBUG: 03:38:55.058: Device reported enroll progress, reported 2 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.058: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.058: Processing command SCAN print-id 188s (process:4408): libfprint-device-DEBUG: 03:38:55.058: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.058: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.058: Device reported enroll progress, reported 3 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.058: Processing command SLEEP 50 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.058: Sleeping 50ms 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.109: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.109: Processing command SCAN print-id 188s (process:4408): libfprint-device-DEBUG: 03:38:55.109: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.109: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.109: Device reported enroll progress, reported 4 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.110: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.110: Processing command RETRY 2 188s (process:4408): libfprint-device-DEBUG: 03:38:55.110: Device reported enroll progress, reported 4 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.110: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.110: Processing command SCAN another-id 188s (process:4408): libfprint-device-DEBUG: 03:38:55.110: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.110: Device reported enroll progress, reported 4 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.110: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.110: Processing command SCAN print-id 188s (process:4408): libfprint-device-DEBUG: 03:38:55.110: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.110: Device reported enroll progress, reported 5 of 5 have been completed 188s (process:4408): libfprint-device-DEBUG: 03:38:55.110: Device reported enroll completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.110: Device reported finger status change: FP_FINGER_STATUS_NONE 188s (process:4408): libfprint-device-DEBUG: 03:38:55.110: Print for finger FP_FINGER_UNKNOWN enrolled 188s (process:4408): libfprint-device-DEBUG: 03:38:55.110: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.110: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.110: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.110: Got instructions of length 5 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.110: Received command CONT 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.110: Processing command CONT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.110: Device reported deletion completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.110: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.111: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.111: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.111: Got instructions of length 16 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.111: Received command SET_KEEP_ALIVE 0 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.111: Keep alive toggled: 0 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.111: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.111: Got instructions of length 19 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.111: Received command SET_ENROLL_STAGES 5 188s (process:4408): libfprint-device-DEBUG: 03:38:55.111: Device reported close completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.111: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.111: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s ok 188s test_enroll_verify_error (__main__.VirtualDeviceStorage.test_enroll_verify_error) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.111: 134919294: ../libfprint/drivers/virtual-device.c:387 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.111: 134919317: ../libfprint/drivers/virtual-device-listener.c:153 188s (process:4408): libfprint-device-DEBUG: 03:38:55.111: Device reported open completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.111: Completing action FPI_DEVICE_ACTION_OPEN in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.111: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.111: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.112: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.112: Received command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.112: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.112: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.112: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.112: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.112: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.112: Device reported enroll progress, reported 1 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.112: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.112: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.112: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.112: Received command SCAN testprint 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.112: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.112: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.112: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.112: Device reported enroll progress, reported 2 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.112: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.112: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.112: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.113: Received command SCAN testprint 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.113: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.113: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.113: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.113: Device reported enroll progress, reported 3 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.113: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.113: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.113: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.113: Received command SCAN testprint 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.113: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.113: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.113: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.113: Device reported enroll progress, reported 4 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.113: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.113: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.113: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.113: Received command SCAN testprint 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.113: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.113: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.114: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.114: Device reported enroll progress, reported 5 of 5 have been completed 188s (process:4408): libfprint-device-DEBUG: 03:38:55.114: Device reported enroll completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.114: Device reported finger status change: FP_FINGER_STATUS_NONE 188s (process:4408): libfprint-device-DEBUG: 03:38:55.114: Print for finger FP_FINGER_LEFT_RING enrolled 188s (process:4408): libfprint-device-DEBUG: 03:38:55.114: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.114: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.114: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.114: Got instructions of length 7 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.114: Received command ERROR 0 188s (process:4408): libfprint-device-DEBUG: 03:38:55.114: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.114: Processing command ERROR 0 188s (process:4408): libfprint-device-DEBUG: 03:38:55.114: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.114: Device reported identify completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.114: Device reported finger status change: FP_FINGER_STATUS_NONE 188s (process:4408): libfprint-device-DEBUG: 03:38:55.114: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.114: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.114: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.114: Got instructions of length 5 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.114: Received command CONT 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.114: Processing command CONT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.114: Device reported deletion completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.114: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.115: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.115: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.115: Got instructions of length 16 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.115: Received command SET_KEEP_ALIVE 0 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.115: Keep alive toggled: 0 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.115: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.115: Got instructions of length 19 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.115: Received command SET_ENROLL_STAGES 5 188s (process:4408): libfprint-device-DEBUG: 03:38:55.115: Device reported close completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.115: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.115: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s Enroll done 188s ok 188s test_enroll_verify_match (__main__.VirtualDeviceStorage.test_enroll_verify_match) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.115: 134923249: ../libfprint/drivers/virtual-device.c:387 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.115: 134923270: ../libfprint/drivers/virtual-device-listener.c:153 188s (process:4408): libfprint-device-DEBUG: 03:38:55.115: Device reported open completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.115: Completing action FPI_DEVICE_ACTION_OPEN in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.115: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.115: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.115: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.115: Received command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.116: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.116: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.116: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.116: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.116: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.116: Device reported enroll progress, reported 1 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.116: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.116: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.116: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.116: Received command SCAN testprint 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.116: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.116: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.116: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.116: Device reported enroll progress, reported 2 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.116: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.116: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.116: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.116: Received command SCAN testprint 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.116: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.116: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.116: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.116: Device reported enroll progress, reported 3 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.116: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.116: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.117: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.117: Received command SCAN testprint 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.117: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.117: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.117: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.117: Device reported enroll progress, reported 4 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.117: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.117: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.117: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.117: Received command SCAN testprint 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.117: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.117: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.117: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.117: Device reported enroll progress, reported 5 of 5 have been completed 188s (process:4408): libfprint-device-DEBUG: 03:38:55.117: Device reported enroll completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.117: Device reported finger status change: FP_FINGER_STATUS_NONE 188s (process:4408): libfprint-device-DEBUG: 03:38:55.117: Print for finger FP_FINGER_LEFT_THUMB enrolled 188s (process:4408): libfprint-device-DEBUG: 03:38:55.117: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.117: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.117: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.117: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.117: Received command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.117: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.117: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.117: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.118: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-virtual_device_storage-DEBUG: 03:38:55.118: Trying to identify print 'testprint' against a gallery of 1 prints 188s (process:4408): libfprint-device-DEBUG: 03:38:55.118: Device reported identify result 188s (process:4408): libfprint-device-DEBUG: 03:38:55.118: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.118: Device reported identify completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.118: Device reported finger status change: FP_FINGER_STATUS_NONE 188s (process:4408): libfprint-device-DEBUG: 03:38:55.118: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.118: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.118: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.118: Got instructions of length 5 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.118: Received command CONT 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.118: Processing command CONT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.118: Device reported deletion completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.118: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.118: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.118: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.118: Got instructions of length 16 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.118: Received command SET_KEEP_ALIVE 0 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.118: Keep alive toggled: 0 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.118: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.118: Got instructions of length 19 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.118: Received command SET_ENROLL_STAGES 5 188s (process:4408): libfprint-device-DEBUG: 03:38:55.118: Device reported close completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.118: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.118: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s Enroll done 188s ok 188s test_enroll_verify_no_match (__main__.VirtualDeviceStorage.test_enroll_verify_no_match) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.119: 134926707: ../libfprint/drivers/virtual-device.c:387 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.119: 134926728: ../libfprint/drivers/virtual-device-listener.c:153 188s (process:4408): libfprint-device-DEBUG: 03:38:55.119: Device reported open completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.119: Completing action FPI_DEVICE_ACTION_OPEN in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.119: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.119: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.119: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.119: Received command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.119: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.119: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.119: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.119: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.119: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.119: Device reported enroll progress, reported 1 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.119: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.119: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.119: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.119: Received command SCAN testprint 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.119: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.119: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.119: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.119: Device reported enroll progress, reported 2 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.119: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.120: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.120: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.120: Received command SCAN testprint 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.120: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.120: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.120: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.120: Device reported enroll progress, reported 3 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.120: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.120: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.120: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.120: Received command SCAN testprint 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.120: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.120: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.120: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.120: Device reported enroll progress, reported 4 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.120: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.120: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.120: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.120: Received command SCAN testprint 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.120: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.120: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.120: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.120: Device reported enroll progress, reported 5 of 5 have been completed 188s (process:4408): libfprint-device-DEBUG: 03:38:55.120: Device reported enroll completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.120: Device reported finger status change: FP_FINGER_STATUS_NONE 188s (process:4408): libfprint-device-DEBUG: 03:38:55.120: Print for finger FP_FINGER_LEFT_RING enrolled 188s (process:4408): libfprint-device-DEBUG: 03:38:55.121: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.121: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.121: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.121: Got instructions of length 18 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.121: Received command SCAN not-testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.121: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.121: Processing command SCAN not-testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.121: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.121: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-virtual_device_storage-DEBUG: 03:38:55.121: Trying to identify print 'not-testprint' against a gallery of 1 prints 188s (process:4408): libfprint-device-DEBUG: 03:38:55.121: Device reported identify result 188s (process:4408): libfprint-device-DEBUG: 03:38:55.121: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.121: Device reported identify completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.121: Device reported finger status change: FP_FINGER_STATUS_NONE 188s (process:4408): libfprint-device-DEBUG: 03:38:55.121: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.121: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.121: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.121: Got instructions of length 5 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.121: Received command CONT 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.121: Processing command CONT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.121: Device reported deletion completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.121: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.121: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.122: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.122: Got instructions of length 16 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.122: Received command SET_KEEP_ALIVE 0 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.122: Keep alive toggled: 0 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.122: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.122: Got instructions of length 19 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.122: Received command SET_ENROLL_STAGES 5 188s (process:4408): libfprint-device-DEBUG: 03:38:55.122: Device reported close completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.122: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.122: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s Enroll done 188s ok 188s test_enroll_verify_retry (__main__.VirtualDeviceStorage.test_enroll_verify_retry) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.122: 134930186: ../libfprint/drivers/virtual-device.c:387 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.122: 134930206: ../libfprint/drivers/virtual-device-listener.c:153 188s (process:4408): libfprint-device-DEBUG: 03:38:55.122: Device reported open completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.122: Completing action FPI_DEVICE_ACTION_OPEN in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.122: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.122: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.122: Got instructions of length 7 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.122: Received command RETRY 1 188s (process:4408): libfprint-device-DEBUG: 03:38:55.122: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.123: Processing command RETRY 1 188s (process:4408): libfprint-device-DEBUG: 03:38:55.123: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.123: Virtual device scan failed with error: The swipe was too short, please try again. 188s (process:4408): libfprint-device-DEBUG: 03:38:55.123: Device reported verify result 188s (process:4408): libfprint-device-DEBUG: 03:38:55.123: Device reported verify completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.123: Device reported finger status change: FP_FINGER_STATUS_NONE 188s (process:4408): libfprint-device-DEBUG: 03:38:55.123: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.123: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.123: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.123: Got instructions of length 5 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.123: Received command CONT 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.123: Processing command CONT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.123: Device reported deletion completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.123: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.123: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.123: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.123: Got instructions of length 16 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.123: Received command SET_KEEP_ALIVE 0 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.123: Keep alive toggled: 0 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.123: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.123: Got instructions of length 19 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.123: Received command SET_ENROLL_STAGES 5 188s (process:4408): libfprint-device-DEBUG: 03:38:55.123: Device reported close completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.123: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.123: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s ok 188s test_enroll_verify_script (__main__.VirtualDeviceStorage.test_enroll_verify_script) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.124: 134931705: ../libfprint/drivers/virtual-device.c:387 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.124: 134931725: ../libfprint/drivers/virtual-device-listener.c:153 188s (process:4408): libfprint-device-DEBUG: 03:38:55.124: Device reported open completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.124: Completing action FPI_DEVICE_ACTION_OPEN in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.124: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.124: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.124: Got instructions of length 19 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.124: Received command SET_ENROLL_STAGES 8 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.124: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.124: Got instructions of length 13 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.124: Received command SCAN print-id 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.124: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.124: Got instructions of length 13 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.124: Received command SCAN print-id 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.124: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.124: Got instructions of length 7 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.124: Received command RETRY 1 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.125: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.125: Got instructions of length 13 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.125: Received command SCAN print-id 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.125: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.125: Got instructions of length 7 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.125: Received command RETRY 3 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.125: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.125: Got instructions of length 13 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.125: Received command SCAN print-id 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.125: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.125: Got instructions of length 7 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.125: Received command RETRY 2 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.125: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.125: Got instructions of length 13 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.125: Received command SCAN print-id 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.125: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.125: Got instructions of length 8 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.125: Received command SLEEP 10 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.126: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.126: Got instructions of length 8 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.126: Received command SLEEP 20 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.126: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.126: Got instructions of length 7 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.126: Received command RETRY 0 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.126: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.126: Got instructions of length 7 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.126: Received command RETRY 3 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.126: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.126: Got instructions of length 13 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.126: Received command SCAN print-id 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.126: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.126: Got instructions of length 15 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.126: Received command SCAN another-id 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.126: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.126: Got instructions of length 13 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.127: Received command SCAN print-id 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.127: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.127: Got instructions of length 13 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.127: Received command SCAN print-id 188s (process:4408): libfprint-device-DEBUG: 03:38:55.127: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.127: Processing command SCAN print-id 188s (process:4408): libfprint-device-DEBUG: 03:38:55.127: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.127: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.127: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.127: Device reported enroll progress, reported 1 of 8 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.127: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.127: Processing command SCAN print-id 188s (process:4408): libfprint-device-DEBUG: 03:38:55.127: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.127: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.127: Device reported enroll progress, reported 2 of 8 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.127: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.127: Processing command RETRY 1 188s (process:4408): libfprint-device-DEBUG: 03:38:55.127: Device reported enroll progress, reported 2 of 8 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.127: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.127: Processing command SCAN print-id 188s (process:4408): libfprint-device-DEBUG: 03:38:55.127: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.127: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.127: Device reported enroll progress, reported 3 of 8 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.127: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.127: Processing command RETRY 3 188s (process:4408): libfprint-device-DEBUG: 03:38:55.127: Device reported enroll progress, reported 3 of 8 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.127: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.127: Processing command SCAN print-id 188s (process:4408): libfprint-device-DEBUG: 03:38:55.127: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.127: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.127: Device reported enroll progress, reported 4 of 8 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.127: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.127: Processing command RETRY 2 188s (process:4408): libfprint-device-DEBUG: 03:38:55.127: Device reported enroll progress, reported 4 of 8 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.127: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.127: Processing command SCAN print-id 188s (process:4408): libfprint-device-DEBUG: 03:38:55.127: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.127: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.127: Device reported enroll progress, reported 5 of 8 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.127: Processing command SLEEP 10 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.127: Sleeping 10ms 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.137: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.137: Processing command SLEEP 20 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.137: Sleeping 20ms 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.158: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.158: Processing command RETRY 0 188s (process:4408): libfprint-device-DEBUG: 03:38:55.158: Device reported enroll progress, reported 5 of 8 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.158: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.158: Processing command RETRY 3 188s (process:4408): libfprint-device-DEBUG: 03:38:55.158: Device reported enroll progress, reported 5 of 8 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.158: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.158: Processing command SCAN print-id 188s (process:4408): libfprint-device-DEBUG: 03:38:55.158: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.158: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.158: Device reported enroll progress, reported 6 of 8 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.158: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.158: Processing command SCAN another-id 188s (process:4408): libfprint-device-DEBUG: 03:38:55.158: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.158: Device reported enroll progress, reported 6 of 8 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.158: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.158: Processing command SCAN print-id 188s (process:4408): libfprint-device-DEBUG: 03:38:55.158: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.158: Device reported enroll progress, reported 7 of 8 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.158: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.158: Processing command SCAN print-id 188s (process:4408): libfprint-device-DEBUG: 03:38:55.158: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.158: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.158: Device reported enroll progress, reported 8 of 8 have been completed 188s (process:4408): libfprint-device-DEBUG: 03:38:55.158: Device reported enroll completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.158: Device reported finger status change: FP_FINGER_STATUS_NONE 188s (process:4408): libfprint-device-DEBUG: 03:38:55.158: Print for finger FP_FINGER_UNKNOWN enrolled 188s (process:4408): libfprint-device-DEBUG: 03:38:55.158: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.158: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.158: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.158: Got instructions of length 7 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.158: Received command RETRY 2 188s (process:4408): libfprint-device-DEBUG: 03:38:55.158: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.158: Processing command RETRY 2 188s (process:4408): libfprint-device-DEBUG: 03:38:55.158: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.158: Virtual device scan failed with error: The finger was not centered properly, please try again. 188s (process:4408): libfprint-device-DEBUG: 03:38:55.158: Device reported verify result 188s (process:4408): libfprint-device-DEBUG: 03:38:55.158: Device reported verify completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.158: Device reported finger status change: FP_FINGER_STATUS_NONE 188s (process:4408): libfprint-device-DEBUG: 03:38:55.158: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.158: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.159: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.159: Got instructions of length 8 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.159: Received command SLEEP 50 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.159: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.159: Got instructions of length 7 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.159: Received command RETRY 1 188s (process:4408): libfprint-device-DEBUG: 03:38:55.159: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.159: Processing command SLEEP 50 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.159: Sleeping 50ms 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.209: Sleeping completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.209: Processing command RETRY 1 188s (process:4408): libfprint-device-DEBUG: 03:38:55.209: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.209: Virtual device scan failed with error: The swipe was too short, please try again. 188s (process:4408): libfprint-device-DEBUG: 03:38:55.209: Device reported verify result 188s (process:4408): libfprint-device-DEBUG: 03:38:55.209: Device reported verify completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.209: Device reported finger status change: FP_FINGER_STATUS_NONE 188s (process:4408): libfprint-device-DEBUG: 03:38:55.209: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.209: Updated temperature model after 0.05 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.209: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.210: Got instructions of length 15 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.210: Received command SCAN another-id 188s (process:4408): libfprint-device-DEBUG: 03:38:55.210: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.210: Processing command SCAN another-id 188s (process:4408): libfprint-device-DEBUG: 03:38:55.210: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.210: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.210: Virtual device scanned print another-id 188s (process:4408): libfprint-device-DEBUG: 03:38:55.210: Device reported verify result 188s (process:4408): libfprint-device-DEBUG: 03:38:55.210: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.210: Device reported verify completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.210: Device reported finger status change: FP_FINGER_STATUS_NONE 188s (process:4408): libfprint-device-DEBUG: 03:38:55.210: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.210: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.210: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.210: Got instructions of length 13 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.210: Received command SCAN print-id 188s (process:4408): libfprint-device-DEBUG: 03:38:55.210: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.210: Processing command SCAN print-id 188s (process:4408): libfprint-device-DEBUG: 03:38:55.210: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.210: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.210: Virtual device scanned print print-id 188s (process:4408): libfprint-device-DEBUG: 03:38:55.210: Device reported verify result 188s (process:4408): libfprint-device-DEBUG: 03:38:55.210: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.210: Device reported verify completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.210: Device reported finger status change: FP_FINGER_STATUS_NONE 188s (process:4408): libfprint-device-DEBUG: 03:38:55.210: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.210: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.211: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.211: Got instructions of length 5 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.211: Received command CONT 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.211: Processing command CONT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.211: Device reported deletion completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.211: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.211: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.211: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.211: Got instructions of length 16 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.211: Received command SET_KEEP_ALIVE 0 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.211: Keep alive toggled: 0 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.211: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.211: Got instructions of length 19 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.211: Received command SET_ENROLL_STAGES 5 188s (process:4408): libfprint-device-DEBUG: 03:38:55.211: Device reported close completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.211: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.211: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s ok 188s test_enroll_with_retry (__main__.VirtualDeviceStorage.test_enroll_with_retry) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.211: 135019528: ../libfprint/drivers/virtual-device.c:387 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.211: 135019550: ../libfprint/drivers/virtual-device-listener.c:153 188s (process:4408): libfprint-device-DEBUG: 03:38:55.212: Device reported open completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.212: Completing action FPI_DEVICE_ACTION_OPEN in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.212: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.212: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.212: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.212: Received command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.212: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.212: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.212: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.212: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.212: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.212: Device reported enroll progress, reported 1 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.212: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.212: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.212: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.212: Received command SCAN testprint 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.212: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.212: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.212: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.212: Device reported enroll progress, reported 2 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.212: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.213: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.213: Got instructions of length 7 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.213: Received command RETRY 1 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.213: Processing command RETRY 1 188s (process:4408): libfprint-device-DEBUG: 03:38:55.213: Device reported enroll progress, reported 2 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.213: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.213: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.213: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.213: Received command SCAN testprint 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.213: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.213: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.213: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.213: Device reported enroll progress, reported 3 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.213: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.213: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.213: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.213: Received command SCAN testprint 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.213: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.213: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.213: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.213: Device reported enroll progress, reported 4 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.213: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.214: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.214: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.214: Received command SCAN testprint 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.214: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.214: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.214: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.214: Device reported enroll progress, reported 5 of 5 have been completed 188s (process:4408): libfprint-device-DEBUG: 03:38:55.214: Device reported enroll completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.214: Device reported finger status change: FP_FINGER_STATUS_NONE 188s (process:4408): libfprint-device-DEBUG: 03:38:55.214: Print for finger FP_FINGER_LEFT_LITTLE enrolled 188s (process:4408): libfprint-device-DEBUG: 03:38:55.214: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.214: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.214: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.214: Got instructions of length 5 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.214: Received command CONT 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.214: Processing command CONT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.214: Device reported deletion completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.214: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.214: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.214: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.214: Got instructions of length 16 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.214: Received command SET_KEEP_ALIVE 0 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.214: Keep alive toggled: 0 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.215: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.215: Got instructions of length 19 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.215: Received command SET_ENROLL_STAGES 5 188s (process:4408): libfprint-device-DEBUG: 03:38:55.215: Device reported close completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.215: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.215: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s Enroll done 188s ok 188s test_finger_status (__main__.VirtualDeviceStorage.test_finger_status) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.215: 135023015: ../libfprint/drivers/virtual-device.c:387 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.215: 135023036: ../libfprint/drivers/virtual-device-listener.c:153 188s (process:4408): libfprint-device-DEBUG: 03:38:55.215: Device reported open completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.215: Completing action FPI_DEVICE_ACTION_OPEN in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.215: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-device-DEBUG: 03:38:55.215: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-device-DEBUG: 03:38:55.215: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.215: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.215: Got instructions of length 8 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.215: Received command FINGER 1 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.215: Processing command FINGER 1 188s (process:4408): libfprint-device-DEBUG: 03:38:55.215: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.216: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.216: Got instructions of length 8 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.216: Received command FINGER 0 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.216: Processing command FINGER 0 188s (process:4408): libfprint-device-DEBUG: 03:38:55.216: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.216: Idle cancelling on ongoing operation! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.216: Got cancellation! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.216: Device reported identify completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.216: Device reported finger status change: FP_FINGER_STATUS_NONE 188s (process:4408): libfprint-device-DEBUG: 03:38:55.216: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.216: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.216: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.216: Got instructions of length 5 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.216: Received command CONT 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.216: Processing command CONT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.216: Device reported deletion completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.216: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.216: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.216: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.216: Got instructions of length 16 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.216: Received command SET_KEEP_ALIVE 0 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.216: Keep alive toggled: 0 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.216: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.217: Got instructions of length 19 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.217: Received command SET_ENROLL_STAGES 5 188s (process:4408): libfprint-device-DEBUG: 03:38:55.217: Device reported close completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.217: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.217: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s ok 188s test_finger_status_after_sleep (__main__.VirtualDeviceStorage.test_finger_status_after_sleep) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.217: 135024927: ../libfprint/drivers/virtual-device.c:387 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.217: 135024948: ../libfprint/drivers/virtual-device-listener.c:153 188s (process:4408): libfprint-device-DEBUG: 03:38:55.217: Device reported open completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.217: Completing action FPI_DEVICE_ACTION_OPEN in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.217: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.217: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.217: Got instructions of length 8 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.217: Received command SLEEP 10 188s (process:4408): libfprint-device-DEBUG: 03:38:55.217: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.217: Processing command SLEEP 10 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.217: Sleeping 10ms 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.227: Sleeping completed 188s (process:4408): libfprint-device-DEBUG: 03:38:55.228: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.228: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.228: Got instructions of length 8 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.228: Received command FINGER 1 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.228: Processing command FINGER 1 188s (process:4408): libfprint-device-DEBUG: 03:38:55.228: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.228: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.228: Got instructions of length 8 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.228: Received command FINGER 0 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.228: Processing command FINGER 0 188s (process:4408): libfprint-device-DEBUG: 03:38:55.228: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.228: Idle cancelling on ongoing operation! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.228: Got cancellation! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.228: Device reported identify completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.228: Device reported finger status change: FP_FINGER_STATUS_NONE 188s (process:4408): libfprint-device-DEBUG: 03:38:55.228: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.228: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.228: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.229: Got instructions of length 5 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.229: Received command CONT 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.229: Processing command CONT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.229: Device reported deletion completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.229: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.229: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.229: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.229: Got instructions of length 16 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.229: Received command SET_KEEP_ALIVE 0 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.229: Keep alive toggled: 0 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.229: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.229: Got instructions of length 19 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.229: Received command SET_ENROLL_STAGES 5 188s (process:4408): libfprint-device-DEBUG: 03:38:55.229: Device reported close completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.229: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.229: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s ok 188s test_identify_match (__main__.VirtualDeviceStorage.test_identify_match) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.229: 135037238: ../libfprint/drivers/virtual-device.c:387 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.229: 135037248: ../libfprint/drivers/virtual-device-listener.c:153 188s (process:4408): libfprint-device-DEBUG: 03:38:55.229: Device reported open completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.229: Completing action FPI_DEVICE_ACTION_OPEN in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.229: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.229: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.229: Got instructions of length 16 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.229: Received command SCAN right-thumb 188s (process:4408): libfprint-device-DEBUG: 03:38:55.230: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.230: Processing command SCAN right-thumb 188s (process:4408): libfprint-device-DEBUG: 03:38:55.230: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.230: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.230: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.230: Device reported enroll progress, reported 1 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.230: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.230: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.230: Got instructions of length 16 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.230: Received command SCAN right-thumb 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.230: Processing command SCAN right-thumb 188s (process:4408): libfprint-device-DEBUG: 03:38:55.230: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.230: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.230: Device reported enroll progress, reported 2 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.230: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.230: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.230: Got instructions of length 16 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.230: Received command SCAN right-thumb 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.230: Processing command SCAN right-thumb 188s (process:4408): libfprint-device-DEBUG: 03:38:55.230: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.230: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.230: Device reported enroll progress, reported 3 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.230: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.230: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.230: Got instructions of length 16 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.230: Received command SCAN right-thumb 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.230: Processing command SCAN right-thumb 188s (process:4408): libfprint-device-DEBUG: 03:38:55.230: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.230: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.230: Device reported enroll progress, reported 4 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.230: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.230: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.230: Got instructions of length 16 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.230: Received command SCAN right-thumb 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.230: Processing command SCAN right-thumb 188s (process:4408): libfprint-device-DEBUG: 03:38:55.230: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.230: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.231: Device reported enroll progress, reported 5 of 5 have been completed 188s (process:4408): libfprint-device-DEBUG: 03:38:55.231: Device reported enroll completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.231: Device reported finger status change: FP_FINGER_STATUS_NONE 188s (process:4408): libfprint-device-DEBUG: 03:38:55.231: Print for finger FP_FINGER_RIGHT_THUMB enrolled 188s (process:4408): libfprint-device-DEBUG: 03:38:55.231: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.231: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.231: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.231: Got instructions of length 15 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.231: Received command SCAN left-thumb 188s (process:4408): libfprint-device-DEBUG: 03:38:55.231: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.231: Processing command SCAN left-thumb 188s (process:4408): libfprint-device-DEBUG: 03:38:55.231: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.231: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.231: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.231: Device reported enroll progress, reported 1 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.231: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.231: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.231: Got instructions of length 15 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.231: Received command SCAN left-thumb 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.231: Processing command SCAN left-thumb 188s (process:4408): libfprint-device-DEBUG: 03:38:55.231: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.231: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.231: Device reported enroll progress, reported 2 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.231: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.231: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.232: Got instructions of length 15 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.232: Received command SCAN left-thumb 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.232: Processing command SCAN left-thumb 188s (process:4408): libfprint-device-DEBUG: 03:38:55.232: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.232: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.232: Device reported enroll progress, reported 3 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.232: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.232: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.232: Got instructions of length 15 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.232: Received command SCAN left-thumb 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.232: Processing command SCAN left-thumb 188s (process:4408): libfprint-device-DEBUG: 03:38:55.232: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.232: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.232: Device reported enroll progress, reported 4 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.232: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.232: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.232: Got instructions of length 15 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.232: Received command SCAN left-thumb 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.232: Processing command SCAN left-thumb 188s (process:4408): libfprint-device-DEBUG: 03:38:55.232: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.232: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.232: Device reported enroll progress, reported 5 of 5 have been completed 188s (process:4408): libfprint-device-DEBUG: 03:38:55.232: Device reported enroll completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.232: Device reported finger status change: FP_FINGER_STATUS_NONE 188s (process:4408): libfprint-device-DEBUG: 03:38:55.232: Print for finger FP_FINGER_LEFT_THUMB enrolled 188s (process:4408): libfprint-device-DEBUG: 03:38:55.232: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.232: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.233: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.233: Got instructions of length 16 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.233: Received command SCAN right-thumb 188s (process:4408): libfprint-device-DEBUG: 03:38:55.233: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.233: Processing command SCAN right-thumb 188s (process:4408): libfprint-device-DEBUG: 03:38:55.233: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.233: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-virtual_device_storage-DEBUG: 03:38:55.233: Trying to identify print 'right-thumb' against a gallery of 2 prints 188s (process:4408): libfprint-device-DEBUG: 03:38:55.233: Device reported identify result 188s (process:4408): libfprint-device-DEBUG: 03:38:55.233: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.233: Device reported identify completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.233: Device reported finger status change: FP_FINGER_STATUS_NONE 188s (process:4408): libfprint-device-DEBUG: 03:38:55.233: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.233: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.233: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.233: Got instructions of length 15 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.233: Received command SCAN left-thumb 188s (process:4408): libfprint-device-DEBUG: 03:38:55.233: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.233: Processing command SCAN left-thumb 188s (process:4408): libfprint-device-DEBUG: 03:38:55.233: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.233: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-virtual_device_storage-DEBUG: 03:38:55.233: Trying to identify print 'left-thumb' against a gallery of 2 prints 188s (process:4408): libfprint-device-DEBUG: 03:38:55.233: Device reported identify result 188s (process:4408): libfprint-device-DEBUG: 03:38:55.233: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.233: Device reported identify completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.233: Device reported finger status change: FP_FINGER_STATUS_NONE 188s (process:4408): libfprint-device-DEBUG: 03:38:55.233: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.233: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.234: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.234: Got instructions of length 5 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.234: Received command CONT 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.234: Processing command CONT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.234: Device reported deletion completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.234: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.234: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.234: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.234: Got instructions of length 16 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.234: Received command SET_KEEP_ALIVE 0 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.234: Keep alive toggled: 0 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.234: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.234: Got instructions of length 19 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.234: Received command SET_ENROLL_STAGES 5 188s (process:4408): libfprint-device-DEBUG: 03:38:55.234: Device reported close completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.234: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.234: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s Enroll done 188s Enroll done 188s ok 188s test_identify_missing_print (__main__.VirtualDeviceStorage.test_identify_missing_print) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.234: 135042512: ../libfprint/drivers/virtual-device.c:387 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.234: 135042534: ../libfprint/drivers/virtual-device-listener.c:153 188s (process:4408): libfprint-device-DEBUG: 03:38:55.235: Device reported open completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.235: Completing action FPI_DEVICE_ACTION_OPEN in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.235: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.235: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.235: Got instructions of length 23 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.235: Received command SCAN not-existing-print 188s (process:4408): libfprint-device-DEBUG: 03:38:55.235: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.235: Processing command SCAN not-existing-print 188s (process:4408): libfprint-device-DEBUG: 03:38:55.235: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.235: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-virtual_device_storage-DEBUG: 03:38:55.235: Trying to identify print 'not-existing-print' against a gallery of 1 prints 188s (process:4408): libfprint-device-DEBUG: 03:38:55.235: Device reported identify result 188s (process:4408): libfprint-device-DEBUG: 03:38:55.235: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.235: Device reported identify completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.235: Device reported finger status change: FP_FINGER_STATUS_NONE 188s (process:4408): libfprint-device-DEBUG: 03:38:55.235: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.235: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.235: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.235: Got instructions of length 5 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.235: Received command CONT 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.235: Processing command CONT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.235: Device reported deletion completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.235: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.235: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.235: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.236: Got instructions of length 16 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.236: Received command SET_KEEP_ALIVE 0 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.236: Keep alive toggled: 0 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.236: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.236: Got instructions of length 19 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.236: Received command SET_ENROLL_STAGES 5 188s (process:4408): libfprint-device-DEBUG: 03:38:55.236: Device reported close completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.236: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.236: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s ok 188s test_identify_no_match (__main__.VirtualDeviceStorage.test_identify_no_match) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.236: 135044257: ../libfprint/drivers/virtual-device.c:387 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.236: 135044279: ../libfprint/drivers/virtual-device-listener.c:153 188s (process:4408): libfprint-device-DEBUG: 03:38:55.236: Device reported open completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.236: Completing action FPI_DEVICE_ACTION_OPEN in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.236: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.236: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.236: Got instructions of length 16 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.237: Received command SCAN right-thumb 188s (process:4408): libfprint-device-DEBUG: 03:38:55.237: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.237: Processing command SCAN right-thumb 188s (process:4408): libfprint-device-DEBUG: 03:38:55.237: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.237: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.237: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.237: Device reported enroll progress, reported 1 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.237: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.237: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.237: Got instructions of length 16 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.237: Received command SCAN right-thumb 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.237: Processing command SCAN right-thumb 188s (process:4408): libfprint-device-DEBUG: 03:38:55.237: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.237: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.237: Device reported enroll progress, reported 2 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.237: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.237: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.237: Got instructions of length 16 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.237: Received command SCAN right-thumb 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.237: Processing command SCAN right-thumb 188s (process:4408): libfprint-device-DEBUG: 03:38:55.237: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.237: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.237: Device reported enroll progress, reported 3 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.237: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.238: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.238: Got instructions of length 16 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.238: Received command SCAN right-thumb 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.238: Processing command SCAN right-thumb 188s (process:4408): libfprint-device-DEBUG: 03:38:55.238: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.238: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.238: Device reported enroll progress, reported 4 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.238: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.238: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.239: Got instructions of length 16 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.239: Received command SCAN right-thumb 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.239: Processing command SCAN right-thumb 188s (process:4408): libfprint-device-DEBUG: 03:38:55.239: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.239: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.239: Device reported enroll progress, reported 5 of 5 have been completed 188s (process:4408): libfprint-device-DEBUG: 03:38:55.239: Device reported enroll completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.239: Device reported finger status change: FP_FINGER_STATUS_NONE 188s (process:4408): libfprint-device-DEBUG: 03:38:55.239: Print for finger FP_FINGER_RIGHT_THUMB enrolled 188s (process:4408): libfprint-device-DEBUG: 03:38:55.239: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.239: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.239: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.239: Got instructions of length 15 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.239: Received command SCAN left-thumb 188s (process:4408): libfprint-device-DEBUG: 03:38:55.239: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.239: Processing command SCAN left-thumb 188s (process:4408): libfprint-device-DEBUG: 03:38:55.239: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.239: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.239: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.239: Device reported enroll progress, reported 1 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.239: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.240: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.240: Got instructions of length 15 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.240: Received command SCAN left-thumb 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.240: Processing command SCAN left-thumb 188s (process:4408): libfprint-device-DEBUG: 03:38:55.240: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.240: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.240: Device reported enroll progress, reported 2 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.240: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.240: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.240: Got instructions of length 15 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.240: Received command SCAN left-thumb 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.240: Processing command SCAN left-thumb 188s (process:4408): libfprint-device-DEBUG: 03:38:55.240: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.240: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.240: Device reported enroll progress, reported 3 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.240: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.240: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.240: Got instructions of length 15 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.240: Received command SCAN left-thumb 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.240: Processing command SCAN left-thumb 188s (process:4408): libfprint-device-DEBUG: 03:38:55.240: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.240: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.241: Device reported enroll progress, reported 4 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.241: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.241: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.241: Got instructions of length 15 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.241: Received command SCAN left-thumb 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.241: Processing command SCAN left-thumb 188s (process:4408): libfprint-device-DEBUG: 03:38:55.241: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.241: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.241: Device reported enroll progress, reported 5 of 5 have been completed 188s (process:4408): libfprint-device-DEBUG: 03:38:55.241: Device reported enroll completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.241: Device reported finger status change: FP_FINGER_STATUS_NONE 188s (process:4408): libfprint-device-DEBUG: 03:38:55.241: Print for finger FP_FINGER_LEFT_THUMB enrolled 188s (process:4408): libfprint-device-DEBUG: 03:38:55.241: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.241: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.241: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.241: Got instructions of length 16 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.241: Received command SCAN right-thumb 188s (process:4408): libfprint-device-DEBUG: 03:38:55.242: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.242: Processing command SCAN right-thumb 188s (process:4408): libfprint-device-DEBUG: 03:38:55.242: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.242: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-virtual_device_storage-DEBUG: 03:38:55.242: Trying to identify print 'right-thumb' against a gallery of 1 prints 188s (process:4408): libfprint-device-DEBUG: 03:38:55.242: Device reported identify result 188s (process:4408): libfprint-device-DEBUG: 03:38:55.242: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.242: Device reported identify completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.242: Device reported finger status change: FP_FINGER_STATUS_NONE 188s (process:4408): libfprint-device-DEBUG: 03:38:55.242: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.242: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.242: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.242: Got instructions of length 15 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.242: Received command SCAN left-thumb 188s (process:4408): libfprint-device-DEBUG: 03:38:55.242: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.242: Processing command SCAN left-thumb 188s (process:4408): libfprint-device-DEBUG: 03:38:55.242: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.242: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-virtual_device_storage-DEBUG: 03:38:55.242: Trying to identify print 'left-thumb' against a gallery of 1 prints 188s (process:4408): libfprint-device-DEBUG: 03:38:55.242: Device reported identify result 188s (process:4408): libfprint-device-DEBUG: 03:38:55.242: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.242: Device reported identify completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.242: Device reported finger status change: FP_FINGER_STATUS_NONE 188s (process:4408): libfprint-device-DEBUG: 03:38:55.242: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.242: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.242: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.243: Got instructions of length 5 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.243: Received command CONT 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.243: Processing command CONT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.243: Device reported deletion completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.243: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.243: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.243: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.243: Got instructions of length 16 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.243: Received command SET_KEEP_ALIVE 0 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.243: Keep alive toggled: 0 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.243: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.243: Got instructions of length 19 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.243: Received command SET_ENROLL_STAGES 5 188s (process:4408): libfprint-device-DEBUG: 03:38:55.243: Device reported close completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.243: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.243: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s Enroll done 188s Enroll done 188s ok 188s test_identify_retry (__main__.VirtualDeviceStorage.test_identify_retry) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.243: 135051481: ../libfprint/drivers/virtual-device.c:387 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.243: 135051504: ../libfprint/drivers/virtual-device-listener.c:153 188s (process:4408): libfprint-device-DEBUG: 03:38:55.243: Device reported open completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.244: Completing action FPI_DEVICE_ACTION_OPEN in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.244: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.244: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.244: Got instructions of length 7 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.244: Received command RETRY 1 188s (process:4408): libfprint-device-DEBUG: 03:38:55.244: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.244: Processing command RETRY 1 188s (process:4408): libfprint-device-DEBUG: 03:38:55.244: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.244: Device reported identify result 188s (process:4408): libfprint-device-DEBUG: 03:38:55.244: Device reported identify completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.244: Device reported finger status change: FP_FINGER_STATUS_NONE 188s (process:4408): libfprint-device-DEBUG: 03:38:55.244: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.244: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.244: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.244: Got instructions of length 5 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.244: Received command CONT 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.244: Processing command CONT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.244: Device reported deletion completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.244: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.244: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.245: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.245: Got instructions of length 16 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.245: Received command SET_KEEP_ALIVE 0 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.245: Keep alive toggled: 0 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.245: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.245: Got instructions of length 19 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.245: Received command SET_ENROLL_STAGES 5 188s (process:4408): libfprint-device-DEBUG: 03:38:55.245: Device reported close completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.245: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.245: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s ok 188s test_identify_unsupported (__main__.VirtualDeviceStorage.test_identify_unsupported) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.245: 135053213: ../libfprint/drivers/virtual-device.c:387 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.245: 135053234: ../libfprint/drivers/virtual-device-listener.c:153 188s (process:4408): libfprint-device-DEBUG: 03:38:55.245: Device reported open completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.245: Completing action FPI_DEVICE_ACTION_OPEN in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.245: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s skipped 'Device supports identification' 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.245: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.245: Got instructions of length 5 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.246: Received command CONT 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.246: Processing command CONT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.246: Device reported deletion completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.246: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.246: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.246: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.246: Got instructions of length 16 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.246: Received command SET_KEEP_ALIVE 0 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.246: Keep alive toggled: 0 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.246: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.246: Got instructions of length 19 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.246: Received command SET_ENROLL_STAGES 5 188s (process:4408): libfprint-device-DEBUG: 03:38:55.246: Device reported close completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.246: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.246: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s test_list_delete (__main__.VirtualDeviceStorage.test_list_delete) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.246: 135054478: ../libfprint/drivers/virtual-device.c:387 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.246: 135054503: ../libfprint/drivers/virtual-device-listener.c:153 188s (process:4408): libfprint-device-DEBUG: 03:38:55.246: Device reported open completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.247: Completing action FPI_DEVICE_ACTION_OPEN in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.247: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.247: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.247: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.247: Received command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.247: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.247: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.247: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.247: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.247: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.247: Device reported enroll progress, reported 1 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.247: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.247: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.247: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.247: Received command SCAN testprint 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.247: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.247: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.247: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.247: Device reported enroll progress, reported 2 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.247: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.247: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.248: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.248: Received command SCAN testprint 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.248: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.248: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.248: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.248: Device reported enroll progress, reported 3 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.248: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.248: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.248: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.248: Received command SCAN testprint 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.248: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.248: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.248: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.248: Device reported enroll progress, reported 4 of 5 have been completed 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.248: Sleeping completed 188s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:55.248: Got a new connection! 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.248: Got instructions of length 14 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.248: Received command SCAN testprint 188s (process:4408): libfprint-virtual_device-DEBUG: 03:38:55.248: Processing command SCAN testprint 188s (process:4408): libfprint-device-DEBUG: 03:38:55.248: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:4408): libfprint-device-DEBUG: 03:38:55.248: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4408): libfprint-device-DEBUG: 03:38:55.248: Device reported enroll progress, reported 5 of 5 have been completed 188s (process:4408): libfprint-device-DEBUG: 03:38:55.248: Device reported enroll completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.248: Device reported finger status change: FP_FINGER_STATUS_NONE 188s (process:4408): libfprint-device-DEBUG: 03:38:55.248: Print for finger FP_FINGER_RIGHT_THUMB enrolled 188s (process:4408): libfprint-device-DEBUG: 03:38:55.248: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.248: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s (process:4408): libfprint-device-DEBUG: 03:38:55.749: Device reported listing completion 188s (process:4408): libfprint-device-DEBUG: 03:38:55.749: Completing action FPI_DEVICE_ACTION_LIST in idle! 188s (process:4408): libfprint-device-DEBUG: 03:38:55.749: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 189s Executing: libfprint-2/virtual-device.test 189s (process:4408): libfprint-virtual_device_storage-DEBUG: 03:38:56.251: Deleting print testprint for user testuser 189s (process:4408): libfprint-device-DEBUG: 03:38:56.251: Device reported deletion completion 189s (process:4408): libfprint-device-DEBUG: 03:38:56.251: Completing action FPI_DEVICE_ACTION_DELETE in idle! 189s (process:4408): libfprint-device-DEBUG: 03:38:56.251: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 189s (process:4408): libfprint-device-DEBUG: 03:38:56.752: Device reported listing completion 189s (process:4408): libfprint-device-DEBUG: 03:38:56.752: Completing action FPI_DEVICE_ACTION_LIST in idle! 189s (process:4408): libfprint-device-DEBUG: 03:38:56.752: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 189s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:56.753: Got a new connection! 189s (process:4408): libfprint-virtual_device-DEBUG: 03:38:56.753: Got instructions of length 5 189s (process:4408): libfprint-virtual_device-DEBUG: 03:38:56.753: Received command CONT 189s (process:4408): libfprint-virtual_device-DEBUG: 03:38:56.753: Processing command CONT 189s (process:4408): libfprint-device-DEBUG: 03:38:56.753: Device reported deletion completion 189s (process:4408): libfprint-device-DEBUG: 03:38:56.753: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 189s (process:4408): libfprint-device-DEBUG: 03:38:56.753: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 189s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:56.753: Got a new connection! 189s (process:4408): libfprint-virtual_device-DEBUG: 03:38:56.753: Got instructions of length 16 189s (process:4408): libfprint-virtual_device-DEBUG: 03:38:56.753: Received command SET_KEEP_ALIVE 0 189s (process:4408): libfprint-virtual_device-DEBUG: 03:38:56.753: Keep alive toggled: 0 189s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:56.753: Got a new connection! 189s (process:4408): libfprint-virtual_device-DEBUG: 03:38:56.753: Got instructions of length 19 189s (process:4408): libfprint-virtual_device-DEBUG: 03:38:56.753: Received command SET_ENROLL_STAGES 5 189s (process:4408): libfprint-device-DEBUG: 03:38:56.753: Device reported close completion 189s (process:4408): libfprint-device-DEBUG: 03:38:56.753: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 189s (process:4408): libfprint-device-DEBUG: 03:38:56.753: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 189s Enroll done 189s 189s blub 'testprint' 189s ok 189s test_list_delete_missing (__main__.VirtualDeviceStorage.test_list_delete_missing) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:56.753: 136561538: ../libfprint/drivers/virtual-device.c:387 189s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:56.753: 136561559: ../libfprint/drivers/virtual-device-listener.c:153 189s (process:4408): libfprint-device-DEBUG: 03:38:56.754: Device reported open completion 189s (process:4408): libfprint-device-DEBUG: 03:38:56.754: Completing action FPI_DEVICE_ACTION_OPEN in idle! 189s (process:4408): libfprint-device-DEBUG: 03:38:56.754: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 189s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:56.754: Got a new connection! 189s (process:4408): libfprint-virtual_device-DEBUG: 03:38:56.754: Got instructions of length 14 189s (process:4408): libfprint-virtual_device-DEBUG: 03:38:56.754: Received command SCAN testprint 189s (process:4408): libfprint-device-DEBUG: 03:38:56.754: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 189s (process:4408): libfprint-virtual_device-DEBUG: 03:38:56.754: Processing command SCAN testprint 189s (process:4408): libfprint-device-DEBUG: 03:38:56.754: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:4408): libfprint-device-DEBUG: 03:38:56.754: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 189s (process:4408): libfprint-device-DEBUG: 03:38:56.754: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:4408): libfprint-device-DEBUG: 03:38:56.754: Device reported enroll progress, reported 1 of 5 have been completed 189s (process:4408): libfprint-virtual_device-DEBUG: 03:38:56.754: Sleeping completed 189s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:56.754: Got a new connection! 189s (process:4408): libfprint-virtual_device-DEBUG: 03:38:56.754: Got instructions of length 14 189s (process:4408): libfprint-virtual_device-DEBUG: 03:38:56.754: Received command SCAN testprint 189s (process:4408): libfprint-virtual_device-DEBUG: 03:38:56.754: Processing command SCAN testprint 189s (process:4408): libfprint-device-DEBUG: 03:38:56.754: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 189s (process:4408): libfprint-device-DEBUG: 03:38:56.754: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:4408): libfprint-device-DEBUG: 03:38:56.754: Device reported enroll progress, reported 2 of 5 have been completed 189s (process:4408): libfprint-virtual_device-DEBUG: 03:38:56.754: Sleeping completed 189s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:56.754: Got a new connection! 189s (process:4408): libfprint-virtual_device-DEBUG: 03:38:56.755: Got instructions of length 14 189s (process:4408): libfprint-virtual_device-DEBUG: 03:38:56.755: Received command SCAN testprint 189s (process:4408): libfprint-virtual_device-DEBUG: 03:38:56.755: Processing command SCAN testprint 189s (process:4408): libfprint-device-DEBUG: 03:38:56.755: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 189s (process:4408): libfprint-device-DEBUG: 03:38:56.755: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:4408): libfprint-device-DEBUG: 03:38:56.755: Device reported enroll progress, reported 3 of 5 have been completed 189s (process:4408): libfprint-virtual_device-DEBUG: 03:38:56.755: Sleeping completed 189s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:56.755: Got a new connection! 189s (process:4408): libfprint-virtual_device-DEBUG: 03:38:56.755: Got instructions of length 14 189s (process:4408): libfprint-virtual_device-DEBUG: 03:38:56.755: Received command SCAN testprint 189s (process:4408): libfprint-virtual_device-DEBUG: 03:38:56.755: Processing command SCAN testprint 189s (process:4408): libfprint-device-DEBUG: 03:38:56.755: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 189s (process:4408): libfprint-device-DEBUG: 03:38:56.755: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:4408): libfprint-device-DEBUG: 03:38:56.755: Device reported enroll progress, reported 4 of 5 have been completed 189s (process:4408): libfprint-virtual_device-DEBUG: 03:38:56.755: Sleeping completed 189s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:56.755: Got a new connection! 189s (process:4408): libfprint-virtual_device-DEBUG: 03:38:56.755: Got instructions of length 14 189s (process:4408): libfprint-virtual_device-DEBUG: 03:38:56.755: Received command SCAN testprint 189s (process:4408): libfprint-virtual_device-DEBUG: 03:38:56.755: Processing command SCAN testprint 189s (process:4408): libfprint-device-DEBUG: 03:38:56.755: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 189s (process:4408): libfprint-device-DEBUG: 03:38:56.755: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:4408): libfprint-device-DEBUG: 03:38:56.755: Device reported enroll progress, reported 5 of 5 have been completed 189s (process:4408): libfprint-device-DEBUG: 03:38:56.755: Device reported enroll completion 189s (process:4408): libfprint-device-DEBUG: 03:38:56.755: Device reported finger status change: FP_FINGER_STATUS_NONE 189s (process:4408): libfprint-device-DEBUG: 03:38:56.755: Print for finger FP_FINGER_RIGHT_THUMB enrolled 189s (process:4408): libfprint-device-DEBUG: 03:38:56.755: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 189s (process:4408): libfprint-device-DEBUG: 03:38:56.755: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 189s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:56.756: Got a new connection! 189s (process:4408): libfprint-virtual_device-DEBUG: 03:38:56.756: Got instructions of length 16 189s (process:4408): libfprint-virtual_device-DEBUG: 03:38:56.756: Received command REMOVE testprint 189s (process:4408): libfprint-virtual_device-DEBUG: 03:38:56.756: Processing command REMOVE testprint 190s (process:4408): libfprint-virtual_device_storage-DEBUG: 03:38:57.257: Deleting print testprint for user testuser 190s (process:4408): libfprint-device-DEBUG: 03:38:57.257: Device reported deletion completion 190s (process:4408): libfprint-device-DEBUG: 03:38:57.257: Completing action FPI_DEVICE_ACTION_DELETE in idle! 190s (process:4408): libfprint-device-DEBUG: 03:38:57.257: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:57.257: Got a new connection! 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.257: Got instructions of length 5 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.257: Received command CONT 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.257: Processing command CONT 190s (process:4408): libfprint-device-DEBUG: 03:38:57.257: Device reported deletion completion 190s (process:4408): libfprint-device-DEBUG: 03:38:57.257: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 190s (process:4408): libfprint-device-DEBUG: 03:38:57.257: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:57.257: Got a new connection! 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.257: Got instructions of length 16 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.257: Received command SET_KEEP_ALIVE 0 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.257: Keep alive toggled: 0 190s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:57.257: Got a new connection! 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.257: Got instructions of length 19 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.257: Received command SET_ENROLL_STAGES 5 190s (process:4408): libfprint-device-DEBUG: 03:38:57.257: Device reported close completion 190s (process:4408): libfprint-device-DEBUG: 03:38:57.257: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s (process:4408): libfprint-device-DEBUG: 03:38:57.257: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s Enroll done 190s ok 190s test_list_empty (__main__.VirtualDeviceStorage.test_list_empty) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.258: 137065625: ../libfprint/drivers/virtual-device.c:387 190s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:57.258: 137065635: ../libfprint/drivers/virtual-device-listener.c:153 190s (process:4408): libfprint-device-DEBUG: 03:38:57.258: Device reported open completion 190s (process:4408): libfprint-device-DEBUG: 03:38:57.258: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s (process:4408): libfprint-device-DEBUG: 03:38:57.258: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s (process:4408): libfprint-device-DEBUG: 03:38:57.758: Device reported listing completion 190s (process:4408): libfprint-device-DEBUG: 03:38:57.758: Completing action FPI_DEVICE_ACTION_LIST in idle! 190s (process:4408): libfprint-device-DEBUG: 03:38:57.758: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:57.759: Got a new connection! 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.759: Got instructions of length 5 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.759: Received command CONT 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.759: Processing command CONT 190s (process:4408): libfprint-device-DEBUG: 03:38:57.759: Device reported deletion completion 190s (process:4408): libfprint-device-DEBUG: 03:38:57.759: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 190s (process:4408): libfprint-device-DEBUG: 03:38:57.759: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:57.759: Got a new connection! 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.759: Got instructions of length 16 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.759: Received command SET_KEEP_ALIVE 0 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.759: Keep alive toggled: 0 190s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:57.760: Got a new connection! 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.760: Got instructions of length 19 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.760: Received command SET_ENROLL_STAGES 5 190s (process:4408): libfprint-device-DEBUG: 03:38:57.760: Device reported close completion 190s (process:4408): libfprint-device-DEBUG: 03:38:57.760: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s (process:4408): libfprint-device-DEBUG: 03:38:57.760: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s ok 190s test_list_error (__main__.VirtualDeviceStorage.test_list_error) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.760: 137568158: ../libfprint/drivers/virtual-device.c:387 190s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:57.760: 137568183: ../libfprint/drivers/virtual-device-listener.c:153 190s (process:4408): libfprint-device-DEBUG: 03:38:57.760: Device reported open completion 190s (process:4408): libfprint-device-DEBUG: 03:38:57.760: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s (process:4408): libfprint-device-DEBUG: 03:38:57.760: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:57.760: Got a new connection! 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.760: Got instructions of length 9 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.760: Received command SLEEP 100 190s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:57.761: Got a new connection! 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.761: Got instructions of length 7 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.761: Received command ERROR 4 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.761: Processing command SLEEP 100 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.761: Sleeping 100ms 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.861: Sleeping completed 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.861: Processing command ERROR 4 190s (process:4408): libfprint-device-DEBUG: 03:38:57.861: Device reported listing completion 190s (process:4408): libfprint-device-DEBUG: 03:38:57.862: Completing action FPI_DEVICE_ACTION_LIST in idle! 190s (process:4408): libfprint-device-DEBUG: 03:38:57.862: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:57.862: Got a new connection! 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.862: Got instructions of length 5 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.862: Received command CONT 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.862: Processing command CONT 190s (process:4408): libfprint-device-DEBUG: 03:38:57.862: Device reported deletion completion 190s (process:4408): libfprint-device-DEBUG: 03:38:57.862: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 190s (process:4408): libfprint-device-DEBUG: 03:38:57.862: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:57.862: Got a new connection! 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.863: Got instructions of length 16 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.863: Received command SET_KEEP_ALIVE 0 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.863: Keep alive toggled: 0 190s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:57.863: Got a new connection! 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.863: Got instructions of length 19 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.863: Received command SET_ENROLL_STAGES 5 190s (process:4408): libfprint-device-DEBUG: 03:38:57.863: Device reported close completion 190s (process:4408): libfprint-device-DEBUG: 03:38:57.863: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s (process:4408): libfprint-device-DEBUG: 03:38:57.863: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s ok 190s test_list_populated (__main__.VirtualDeviceStorage.test_list_populated) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.863: 137671200: ../libfprint/drivers/virtual-device.c:387 190s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:57.863: 137671226: ../libfprint/drivers/virtual-device-listener.c:153 190s (process:4408): libfprint-device-DEBUG: 03:38:57.863: Device reported open completion 190s (process:4408): libfprint-device-DEBUG: 03:38:57.863: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s (process:4408): libfprint-device-DEBUG: 03:38:57.863: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:57.863: Got a new connection! 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.863: Got instructions of length 9 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.864: Received command INSERT p1 190s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:57.864: Got a new connection! 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.864: Got instructions of length 7 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.864: Received command SCAN p2 190s (process:4408): libfprint-device-DEBUG: 03:38:57.864: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.864: Processing command INSERT p1 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.864: Processing command SCAN p2 190s (process:4408): libfprint-device-DEBUG: 03:38:57.864: Device reported finger status change: FP_FINGER_STATUS_NEEDED 190s (process:4408): libfprint-device-DEBUG: 03:38:57.864: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 190s (process:4408): libfprint-device-DEBUG: 03:38:57.864: Device reported finger status change: FP_FINGER_STATUS_NEEDED 190s (process:4408): libfprint-device-DEBUG: 03:38:57.864: Device reported enroll progress, reported 1 of 5 have been completed 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.864: Sleeping completed 190s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:57.864: Got a new connection! 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.864: Got instructions of length 7 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.864: Received command SCAN p2 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.864: Processing command SCAN p2 190s (process:4408): libfprint-device-DEBUG: 03:38:57.864: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 190s (process:4408): libfprint-device-DEBUG: 03:38:57.864: Device reported finger status change: FP_FINGER_STATUS_NEEDED 190s (process:4408): libfprint-device-DEBUG: 03:38:57.864: Device reported enroll progress, reported 2 of 5 have been completed 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.864: Sleeping completed 190s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:57.865: Got a new connection! 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.865: Got instructions of length 7 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.865: Received command SCAN p2 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.865: Processing command SCAN p2 190s (process:4408): libfprint-device-DEBUG: 03:38:57.865: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 190s (process:4408): libfprint-device-DEBUG: 03:38:57.865: Device reported finger status change: FP_FINGER_STATUS_NEEDED 190s (process:4408): libfprint-device-DEBUG: 03:38:57.865: Device reported enroll progress, reported 3 of 5 have been completed 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.865: Sleeping completed 190s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:57.865: Got a new connection! 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.865: Got instructions of length 7 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.865: Received command SCAN p2 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.865: Processing command SCAN p2 190s (process:4408): libfprint-device-DEBUG: 03:38:57.865: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 190s (process:4408): libfprint-device-DEBUG: 03:38:57.865: Device reported finger status change: FP_FINGER_STATUS_NEEDED 190s (process:4408): libfprint-device-DEBUG: 03:38:57.865: Device reported enroll progress, reported 4 of 5 have been completed 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.865: Sleeping completed 190s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:57.865: Got a new connection! 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.865: Got instructions of length 7 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.865: Received command SCAN p2 190s (process:4408): libfprint-virtual_device-DEBUG: 03:38:57.865: Processing command SCAN p2 190s (process:4408): libfprint-device-DEBUG: 03:38:57.865: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 190s (process:4408): libfprint-device-DEBUG: 03:38:57.865: Device reported finger status change: FP_FINGER_STATUS_NEEDED 190s (process:4408): libfprint-device-DEBUG: 03:38:57.866: Device reported enroll progress, reported 5 of 5 have been completed 190s (process:4408): libfprint-device-DEBUG: 03:38:57.866: Device reported enroll completion 190s (process:4408): libfprint-device-DEBUG: 03:38:57.866: Device reported finger status change: FP_FINGER_STATUS_NONE 190s (process:4408): libfprint-device-DEBUG: 03:38:57.866: Print for finger FP_FINGER_LEFT_LITTLE enrolled 190s (process:4408): libfprint-device-DEBUG: 03:38:57.866: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 190s (process:4408): libfprint-device-DEBUG: 03:38:57.866: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:4408): libfprint-device-DEBUG: 03:38:58.367: Device reported listing completion 191s (process:4408): libfprint-device-DEBUG: 03:38:58.367: Completing action FPI_DEVICE_ACTION_LIST in idle! 191s (process:4408): libfprint-device-DEBUG: 03:38:58.367: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:58.367: Got a new connection! 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.367: Got instructions of length 5 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.367: Received command CONT 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.367: Processing command CONT 191s (process:4408): libfprint-device-DEBUG: 03:38:58.367: Device reported deletion completion 191s (process:4408): libfprint-device-DEBUG: 03:38:58.367: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 191s (process:4408): libfprint-device-DEBUG: 03:38:58.367: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:58.368: Got a new connection! 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.368: Got instructions of length 16 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.368: Received command SET_KEEP_ALIVE 0 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.368: Keep alive toggled: 0 191s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:58.368: Got a new connection! 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.368: Got instructions of length 19 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.368: Received command SET_ENROLL_STAGES 5 191s (process:4408): libfprint-device-DEBUG: 03:38:58.368: Device reported close completion 191s (process:4408): libfprint-device-DEBUG: 03:38:58.368: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s (process:4408): libfprint-device-DEBUG: 03:38:58.368: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s Enroll done 191s ok 191s test_open_error (__main__.VirtualDeviceStorage.test_open_error) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.368: 138176266: ../libfprint/drivers/virtual-device.c:387 191s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:58.368: 138176290: ../libfprint/drivers/virtual-device-listener.c:153 191s (process:4408): libfprint-device-DEBUG: 03:38:58.368: Device reported open completion 191s (process:4408): libfprint-device-DEBUG: 03:38:58.368: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s (process:4408): libfprint-device-DEBUG: 03:38:58.368: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:58.368: Got a new connection! 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.369: Got instructions of length 16 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.369: Received command IGNORED_COMMAND 191s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:58.369: Got a new connection! 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.369: Got instructions of length 7 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.369: Received command ERROR 5 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.369: Processing command IGNORED_COMMAND 191s (process:4408): libfprint-device-DEBUG: 03:38:58.369: Device reported close completion 191s (process:4408): libfprint-device-DEBUG: 03:38:58.369: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s (process:4408): libfprint-device-DEBUG: 03:38:58.369: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.369: 138177302: ../libfprint/drivers/virtual-device.c:387 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.369: Processing command ERROR 5 191s (process:4408): libfprint-device-DEBUG: 03:38:58.369: Device reported open completion 191s (process:4408): libfprint-device-DEBUG: 03:38:58.369: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s (process:4408): libfprint-device-DEBUG: 03:38:58.369: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s ok 191s test_open_error_with_keep_alive (__main__.VirtualDeviceStorage.test_open_error_with_keep_alive) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.369: 138177534: ../libfprint/drivers/virtual-device.c:387 191s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:58.369: 138177556: ../libfprint/drivers/virtual-device-listener.c:153 191s (process:4408): libfprint-device-DEBUG: 03:38:58.370: Device reported open completion 191s (process:4408): libfprint-device-DEBUG: 03:38:58.370: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s (process:4408): libfprint-device-DEBUG: 03:38:58.370: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:58.370: Got a new connection! 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.370: Got instructions of length 16 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.370: Received command SET_KEEP_ALIVE 1 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.370: Keep alive toggled: 1 191s (process:4408): libfprint-device-DEBUG: 03:38:58.370: Device reported close completion 191s (process:4408): libfprint-device-DEBUG: 03:38:58.370: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s (process:4408): libfprint-device-DEBUG: 03:38:58.370: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:58.370: Got a new connection! 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.370: Got instructions of length 7 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.370: Received command ERROR 5 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.370: 138178330: ../libfprint/drivers/virtual-device.c:387 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.370: Processing command ERROR 5 191s (process:4408): libfprint-device-DEBUG: 03:38:58.370: Device reported open completion 191s (process:4408): libfprint-device-DEBUG: 03:38:58.370: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s (process:4408): libfprint-device-DEBUG: 03:38:58.370: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s ok 191s test_quick_enroll (__main__.VirtualDeviceStorage.test_quick_enroll) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.370: 138178526: ../libfprint/drivers/virtual-device.c:387 191s (process:4408): libfprint-device-DEBUG: 03:38:58.370: Device reported open completion 191s (process:4408): libfprint-device-DEBUG: 03:38:58.370: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s (process:4408): libfprint-device-DEBUG: 03:38:58.370: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:58.371: Got a new connection! 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.371: Got instructions of length 19 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.371: Received command SET_ENROLL_STAGES 1 191s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:58.371: Got a new connection! 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.371: Got instructions of length 14 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.371: Received command SCAN testprint 191s (process:4408): libfprint-device-DEBUG: 03:38:58.371: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.371: Processing command SCAN testprint 191s (process:4408): libfprint-device-DEBUG: 03:38:58.371: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:4408): libfprint-device-DEBUG: 03:38:58.371: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 191s (process:4408): libfprint-device-DEBUG: 03:38:58.371: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:4408): libfprint-device-DEBUG: 03:38:58.371: Device reported enroll progress, reported 1 of 1 have been completed 191s (process:4408): libfprint-device-DEBUG: 03:38:58.371: Device reported enroll completion 191s (process:4408): libfprint-device-DEBUG: 03:38:58.371: Device reported finger status change: FP_FINGER_STATUS_NONE 191s (process:4408): libfprint-device-DEBUG: 03:38:58.371: Print for finger FP_FINGER_LEFT_LITTLE enrolled 191s (process:4408): libfprint-device-DEBUG: 03:38:58.371: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 191s (process:4408): libfprint-device-DEBUG: 03:38:58.371: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:58.371: Got a new connection! 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.371: Got instructions of length 5 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.371: Received command CONT 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.372: Processing command CONT 191s (process:4408): libfprint-device-DEBUG: 03:38:58.372: Device reported deletion completion 191s (process:4408): libfprint-device-DEBUG: 03:38:58.372: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 191s (process:4408): libfprint-device-DEBUG: 03:38:58.372: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:58.372: Got a new connection! 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.372: Got instructions of length 16 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.372: Received command SET_KEEP_ALIVE 0 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.372: Keep alive toggled: 0 191s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:58.372: Got a new connection! 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.372: Got instructions of length 19 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.372: Received command SET_ENROLL_STAGES 5 191s (process:4408): libfprint-device-DEBUG: 03:38:58.372: Device reported close completion 191s (process:4408): libfprint-device-DEBUG: 03:38:58.372: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s (process:4408): libfprint-device-DEBUG: 03:38:58.372: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s Enroll done 191s ok 191s test_verify_missing_print (__main__.VirtualDeviceStorage.test_verify_missing_print) ... (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.372: 138180359: ../libfprint/drivers/virtual-device.c:387 191s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:58.372: 138180379: ../libfprint/drivers/virtual-device-listener.c:153 191s (process:4408): libfprint-device-DEBUG: 03:38:58.372: Device reported open completion 191s (process:4408): libfprint-device-DEBUG: 03:38:58.372: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s (process:4408): libfprint-device-DEBUG: 03:38:58.372: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:58.373: Got a new connection! 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.373: Got instructions of length 23 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.373: Received command SCAN not-existing-print 191s (process:4408): libfprint-device-DEBUG: 03:38:58.373: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.373: Processing command SCAN not-existing-print 191s (process:4408): libfprint-device-DEBUG: 03:38:58.373: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:4408): libfprint-device-DEBUG: 03:38:58.373: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.373: Virtual device scanned print not-existing-print 191s (process:4408): libfprint-device-DEBUG: 03:38:58.373: Device reported verify result 191s (process:4408): libfprint-device-DEBUG: 03:38:58.373: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:4408): libfprint-device-DEBUG: 03:38:58.373: Device reported verify completion 191s (process:4408): libfprint-device-DEBUG: 03:38:58.373: Device reported finger status change: FP_FINGER_STATUS_NONE 191s (process:4408): libfprint-device-DEBUG: 03:38:58.373: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 191s (process:4408): libfprint-device-DEBUG: 03:38:58.373: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:58.373: Got a new connection! 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.373: Got instructions of length 5 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.373: Received command CONT 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.373: Processing command CONT 191s (process:4408): libfprint-device-DEBUG: 03:38:58.373: Device reported deletion completion 191s (process:4408): libfprint-device-DEBUG: 03:38:58.373: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 191s (process:4408): libfprint-device-DEBUG: 03:38:58.373: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:58.373: Got a new connection! 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.373: Got instructions of length 16 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.373: Received command SET_KEEP_ALIVE 0 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.373: Keep alive toggled: 0 191s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:58.373: Got a new connection! 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.374: Got instructions of length 19 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.374: Received command SET_ENROLL_STAGES 5 191s (process:4408): libfprint-device-DEBUG: 03:38:58.374: Device reported close completion 191s (process:4408): libfprint-device-DEBUG: 03:38:58.374: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s (process:4408): libfprint-device-DEBUG: 03:38:58.374: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s ok 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.374: 138182104: ../libfprint/drivers/virtual-device.c:752 191s test_device_unplug (__main__.VirtualDeviceUnplugging.test_device_unplug) ... (process:4408): libfprint-context-DEBUG: 03:38:58.374: Initializing FpContext (libfprint version 1.94.8+tod1) 191s (process:4408): libfprint-tod-DEBUG: 03:38:58.374: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 191s (process:4408): libfprint-context-DEBUG: 03:38:58.378: No driver found for USB device 1D6B:0003 191s (process:4408): libfprint-context-DEBUG: 03:38:58.378: No driver found for USB device 0627:0001 191s (process:4408): libfprint-context-DEBUG: 03:38:58.378: No driver found for USB device 0627:0001 191s (process:4408): libfprint-context-DEBUG: 03:38:58.378: No driver found for USB device 1D6B:0002 191s (process:4408): libfprint-context-DEBUG: 03:38:58.378: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-khd29lh4/virtual-device.socket 191s (process:4408): libfprint-context-DEBUG: 03:38:58.378: created 191s (process:4408): libfprint-context-DEBUG: 03:38:58.378: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-r_zxfgk8/virtual-device-storage.socket 191s (process:4408): libfprint-context-DEBUG: 03:38:58.378: created 191s (process:4408): libfprint-device-DEBUG: 03:38:58.379: Device reported probe completion 191s (process:4408): libfprint-device-DEBUG: 03:38:58.379: Device reported probe completion 191s (process:4408): libfprint-device-DEBUG: 03:38:58.379: Completing action FPI_DEVICE_ACTION_PROBE in idle! 191s (process:4408): libfprint-device-DEBUG: 03:38:58.379: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s (process:4408): libfprint-device-DEBUG: 03:38:58.379: Completing action FPI_DEVICE_ACTION_PROBE in idle! 191s (process:4408): libfprint-device-DEBUG: 03:38:58.379: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.379: 138187381: ../libfprint/drivers/virtual-device.c:387 191s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:58.379: 138187391: ../libfprint/drivers/virtual-device-listener.c:153 191s (process:4408): libfprint-device-DEBUG: 03:38:58.379: Device reported open completion 191s (process:4408): libfprint-device-DEBUG: 03:38:58.379: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s (process:4408): libfprint-device-DEBUG: 03:38:58.379: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:58.380: Got a new connection! 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.380: Got instructions of length 7 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.380: Received command UNPLUG 191s (process:4408): libfprint-device-DEBUG: 03:38:58.380: Device reported close completion 191s (process:4408): libfprint-device-DEBUG: 03:38:58.380: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s (process:4408): libfprint-device-DEBUG: 03:38:58.380: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.380: 138188279: ../libfprint/drivers/virtual-device.c:752 191s (process:4408): libfprint-virtual_device_storage-DEBUG: 03:38:58.380: 138188306: ../libfprint/drivers/virtual-device-storage.c:253 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.380: 138188314: ../libfprint/drivers/virtual-device.c:752 191s ok 191s test_device_unplug_during_verify (__main__.VirtualDeviceUnplugging.test_device_unplug_during_verify) ... (process:4408): libfprint-context-DEBUG: 03:38:58.380: Initializing FpContext (libfprint version 1.94.8+tod1) 191s (process:4408): libfprint-tod-DEBUG: 03:38:58.380: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 191s (process:4408): libfprint-context-DEBUG: 03:38:58.384: No driver found for USB device 1D6B:0003 191s (process:4408): libfprint-context-DEBUG: 03:38:58.384: No driver found for USB device 0627:0001 191s (process:4408): libfprint-context-DEBUG: 03:38:58.384: No driver found for USB device 0627:0001 191s (process:4408): libfprint-context-DEBUG: 03:38:58.384: No driver found for USB device 1D6B:0002 191s (process:4408): libfprint-context-DEBUG: 03:38:58.384: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-khd29lh4/virtual-device.socket 191s (process:4408): libfprint-context-DEBUG: 03:38:58.384: created 191s (process:4408): libfprint-context-DEBUG: 03:38:58.384: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-r_zxfgk8/virtual-device-storage.socket 191s (process:4408): libfprint-context-DEBUG: 03:38:58.384: created 191s (process:4408): libfprint-device-DEBUG: 03:38:58.385: Device reported probe completion 191s (process:4408): libfprint-device-DEBUG: 03:38:58.385: Device reported probe completion 191s (process:4408): libfprint-device-DEBUG: 03:38:58.385: Completing action FPI_DEVICE_ACTION_PROBE in idle! 191s (process:4408): libfprint-device-DEBUG: 03:38:58.385: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s (process:4408): libfprint-device-DEBUG: 03:38:58.386: Completing action FPI_DEVICE_ACTION_PROBE in idle! 191s (process:4408): libfprint-device-DEBUG: 03:38:58.386: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.386: 138193717: ../libfprint/drivers/virtual-device.c:387 191s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:58.386: 138193742: ../libfprint/drivers/virtual-device-listener.c:153 191s (process:4408): libfprint-device-DEBUG: 03:38:58.386: Device reported open completion 191s (process:4408): libfprint-device-DEBUG: 03:38:58.386: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s (process:4408): libfprint-device-DEBUG: 03:38:58.386: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s (process:4408): libfprint-device-DEBUG: 03:38:58.386: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s (process:4408): libfprint-device-DEBUG: 03:38:58.386: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:4408): libfprint-virtual_device_connection-DEBUG: 03:38:58.386: Got a new connection! 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.386: Got instructions of length 7 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.386: Received command UNPLUG 191s (process:4408): libfprint-device-DEBUG: 03:38:58.486: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 191s (process:4408): libfprint-device-DEBUG: 03:38:58.887: Device reported generic error (No commands arrived in time to run!) during action; action was: FPI_DEVICE_ACTION_VERIFY 191s (process:4408): libfprint-device-DEBUG: 03:38:58.887: Device reported verify completion 191s (process:4408): libfprint-device-DEBUG: 03:38:58.887: Device reported finger status change: FP_FINGER_STATUS_NONE 191s (process:4408): libfprint-device-DEBUG: 03:38:58.887: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 191s (process:4408): libfprint-device-DEBUG: 03:38:58.887: Updated temperature model after 0.40 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:4408): libfprint-device-DEBUG: 03:38:58.888: Device reported close completion 191s (process:4408): libfprint-device-DEBUG: 03:38:58.888: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s (process:4408): libfprint-device-DEBUG: 03:38:58.888: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.888: 138695970: ../libfprint/drivers/virtual-device.c:752 191s (process:4408): libfprint-virtual_device_storage-DEBUG: 03:38:58.888: 138696045: ../libfprint/drivers/virtual-device-storage.c:253 191s (process:4408): libfprint-virtual_device-DEBUG: 03:38:58.888: 138696077: ../libfprint/drivers/virtual-device.c:752 191s ok 191s 191s ---------------------------------------------------------------------- 191s Ran 86 tests in 17.600s 191s 191s OK (skipped=1) 191s PASS: libfprint-2/virtual-device.test 191s Running test: libfprint-2/driver-focaltech_moc.test 191s ** (umockdev-run:4426): DEBUG: 03:38:58.945: umockdev.vala:127: Created udev test bed /tmp/umockdev.Q51K22 191s ** (umockdev-run:4426): DEBUG: 03:38:58.945: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1/3-1.4 191s ** (umockdev-run:4426): DEBUG: 03:38:58.949: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1/3-1.4 (subsystem usb) 191s ** (umockdev-run:4426): DEBUG: 03:38:58.952: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.Q51K22/dev/bus/usb/003/006 191s ** (umockdev-run:4426): DEBUG: 03:38:58.953: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1 191s ** (umockdev-run:4426): DEBUG: 03:38:58.956: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1 (subsystem usb) 191s ** (umockdev-run:4426): DEBUG: 03:38:58.959: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.Q51K22/dev/bus/usb/003/002 191s ** (umockdev-run:4426): DEBUG: 03:38:58.959: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3 191s ** (umockdev-run:4426): DEBUG: 03:38:58.963: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3 (subsystem usb) 191s ** (umockdev-run:4426): DEBUG: 03:38:58.965: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.Q51K22/dev/bus/usb/003/001 191s ** (umockdev-run:4426): DEBUG: 03:38:58.966: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0 191s ** (umockdev-run:4426): DEBUG: 03:38:58.967: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0 (subsystem pci) 191s ** (umockdev-run:4426): DEBUG: 03:38:58.970: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4 191s ** (umockdev-run:4426): DEBUG: 03:38:58.971: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4 (subsystem pci) 192s (process:4430): libfprint-context-DEBUG: 03:38:59.057: Initializing FpContext (libfprint version 1.94.8+tod1) 192s (process:4430): libfprint-tod-DEBUG: 03:38:59.057: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 192s (process:4430): libfprint-focaltech_moc-DEBUG: 03:38:59.060: 138868431: ../libfprint/drivers/focaltech_moc/focaltech_moc.c:1849 192s (process:4430): libfprint-context-DEBUG: 03:38:59.061: No driver found for USB device 05E3:0608 192s (process:4430): libfprint-context-DEBUG: 03:38:59.061: No driver found for USB device 1D6B:0002 192s (process:4430): libfprint-device-DEBUG: 03:38:59.061: Device reported probe completion 192s (process:4430): libfprint-device-DEBUG: 03:38:59.061: Completing action FPI_DEVICE_ACTION_PROBE in idle! 192s (process:4430): libfprint-device-DEBUG: 03:38:59.061: Not updating temperature model, device can run continuously! 192s libusb: warning [read_sysfs_attr] attribute bConfigurationValue doesn't end with newline? 192s libusb: warning [read_sysfs_attr] attribute bConfigurationValue doesn't end with newline? 192s (process:4430): libfprint-focaltech_moc-DEBUG: 03:38:59.063: class:dc, subclass:a0, protocol:b0 192s (process:4430): libfprint-focaltech_moc-DEBUG: 03:38:59.063: bytes size:0 192s (process:4430): libfprint-focaltech_moc-DEBUG: 03:38:59.063: 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 192s (process:4430): libfprint-focaltech_moc-DEBUG: 03:38:59.063: bytes size:0 192s (process:4430): libfprint-focaltech_moc-DEBUG: 03:38:59.063: 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 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.063: [focaltech_moc] DEV_INIT_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.063: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.064: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 192s (process:4430): libfprint-focaltech_moc-DEBUG: 03:38:59.064: focaltechmoc enroll_times: 10 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.065: [focaltech_moc] DEV_INIT_STATES entering state 1 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.065: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.065: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.065: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.066: [focaltech_moc] DEV_INIT_STATES completed successfully 192s (process:4430): libfprint-device-DEBUG: 03:38:59.066: Device reported open completion 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.066: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 192s (process:4430): libfprint-device-DEBUG: 03:38:59.066: Completing action FPI_DEVICE_ACTION_OPEN in idle! 192s (process:4430): libfprint-device-DEBUG: 03:38:59.066: Not updating temperature model, device can run continuously! 192s (process:4430): libfprint-device-DEBUG: 03:38:59.067: Not updating temperature model, device can run continuously! 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.067: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.067: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.068: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.068: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 1 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.068: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.069: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.069: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.069: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 2 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.070: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.070: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.070: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.071: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 3 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.071: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.071: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.071: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 192s (process:4430): libfprint-focaltech_moc-DEBUG: 03:38:59.072: focaltechmoc user id: FP1-00000000-0-00000000-nobody 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.072: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.072: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.072: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.072: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.074: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.074: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.124: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.124: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.125: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.125: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.125: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.175: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.176: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.180: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.180: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.180: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.231: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.231: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.231: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.232: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.232: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.282: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.282: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.283: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.284: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.284: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.334: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.334: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.335: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.336: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.336: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.386: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.386: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.387: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.389: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.389: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.390: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.390: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 192s (process:4430): libfprint-device-DEBUG: 03:38:59.390: Device reported enroll progress, reported 1 of 10 have been completed 192s (process:4430): libfprint-focaltech_moc-DEBUG: 03:38:59.390: focaltechmoc remain: 9 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.390: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.390: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.391: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.391: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.392: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.392: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.442: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.442: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.442: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.443: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.443: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.493: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.493: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.494: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.494: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.494: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.544: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.544: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.545: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.546: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.546: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.596: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.596: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.596: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.597: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.597: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.647: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.647: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.648: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.651: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.651: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.651: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.652: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 192s (process:4430): libfprint-device-DEBUG: 03:38:59.653: Device reported enroll progress, reported 2 of 10 have been completed 192s (process:4430): libfprint-focaltech_moc-DEBUG: 03:38:59.653: focaltechmoc remain: 8 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.653: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.653: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.654: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.654: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.655: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.655: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.705: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.705: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.706: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.706: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.706: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.707: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.707: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 192s (process:4430): libfprint-device-DEBUG: 03:38:59.707: Device reported enroll progress, reported 3 of 10 have been completed 192s (process:4430): libfprint-focaltech_moc-DEBUG: 03:38:59.708: focaltechmoc remain: 7 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.708: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.708: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.708: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.708: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.709: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.709: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.759: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.759: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.759: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.760: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.760: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.810: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.810: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.811: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.811: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.811: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.861: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.861: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.862: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.863: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.863: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.913: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.913: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.914: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.915: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.915: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.965: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.965: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.965: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.966: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.966: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.966: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.967: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 192s (process:4430): libfprint-device-DEBUG: 03:38:59.967: Device reported enroll progress, reported 4 of 10 have been completed 192s (process:4430): libfprint-focaltech_moc-DEBUG: 03:38:59.967: focaltechmoc remain: 6 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.967: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.967: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.968: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.968: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.969: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 192s (process:4430): libfprint-SSM-DEBUG: 03:38:59.969: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.019: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.019: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.019: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.020: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.020: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.070: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.070: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.071: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.071: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.071: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.122: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.122: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.123: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.123: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.123: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.124: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.124: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-device-DEBUG: 03:39:00.124: Device reported enroll progress, reported 5 of 10 have been completed 193s (process:4430): libfprint-focaltech_moc-DEBUG: 03:39:00.124: focaltechmoc remain: 5 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.124: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.124: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.125: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.125: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.125: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.126: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.176: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.176: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.176: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.177: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.177: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.227: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.227: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.227: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.228: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.228: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.278: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.278: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.279: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.280: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.280: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.330: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.330: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.330: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.331: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.331: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.331: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.332: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-device-DEBUG: 03:39:00.332: Device reported enroll progress, reported 6 of 10 have been completed 193s (process:4430): libfprint-focaltech_moc-DEBUG: 03:39:00.332: focaltechmoc remain: 4 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.332: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.332: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.333: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.333: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.333: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.333: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.334: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.334: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-device-DEBUG: 03:39:00.335: Device reported enroll progress, reported 6 of 10 have been completed 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.335: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.335: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.335: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.335: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.340: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.340: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.390: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.390: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.390: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.391: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.391: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.441: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.441: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.442: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.442: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.442: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.492: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.492: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.493: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.493: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.493: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.544: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.544: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.544: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.545: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.545: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.545: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.545: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-device-DEBUG: 03:39:00.546: Device reported enroll progress, reported 7 of 10 have been completed 193s (process:4430): libfprint-focaltech_moc-DEBUG: 03:39:00.546: focaltechmoc remain: 3 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.546: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.546: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.546: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.546: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.548: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.548: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.598: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.598: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.598: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.599: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.599: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.649: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.649: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.650: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.650: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.650: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.650: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.651: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-device-DEBUG: 03:39:00.651: Device reported enroll progress, reported 8 of 10 have been completed 193s (process:4430): libfprint-focaltech_moc-DEBUG: 03:39:00.651: focaltechmoc remain: 2 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.651: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.651: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.652: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.652: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.652: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.652: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.703: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.703: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.703: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.704: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.704: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.708: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.708: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-device-DEBUG: 03:39:00.709: Device reported enroll progress, reported 9 of 10 have been completed 193s (process:4430): libfprint-focaltech_moc-DEBUG: 03:39:00.709: focaltechmoc remain: 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.709: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.709: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.709: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.709: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.710: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.710: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.760: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.760: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.761: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.761: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.761: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.762: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.762: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-device-DEBUG: 03:39:00.762: Device reported enroll progress, reported 10 of 10 have been completed 193s (process:4430): libfprint-focaltech_moc-DEBUG: 03:39:00.762: focaltechmoc remain: 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.762: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 7 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.762: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.763: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.763: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.764: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 8 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.764: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.768: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.768: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-focaltech_moc-DEBUG: 03:39:00.768: focaltech_moc_commit_cb success 193s (process:4430): libfprint-focaltech_moc-DEBUG: 03:39:00.768: Enrollment was successful! 193s (process:4430): libfprint-device-DEBUG: 03:39:00.768: Device reported enroll completion 193s (process:4430): libfprint-device-DEBUG: 03:39:00.768: Print for finger FP_FINGER_UNKNOWN enrolled 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.768: [focaltech_moc] MOC_ENROLL_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.768: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-device-DEBUG: 03:39:00.768: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 193s (process:4430): libfprint-device-DEBUG: 03:39:00.769: Not updating temperature model, device can run continuously! 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.769: [focaltech_moc] MOC_LIST_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.769: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.769: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.770: [focaltech_moc] MOC_LIST_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.770: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.770: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.770: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-focaltech_moc-DEBUG: 03:39:00.771: focaltechmoc add slot: 0 193s (process:4430): libfprint-focaltech_moc-DEBUG: 03:39:00.771: FP1-00000000-0-00000000-nobody 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.771: [focaltech_moc] MOC_LIST_NUM_STATES entering state 2 193s (process:4430): libfprint-device-DEBUG: 03:39:00.771: Device reported listing completion 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.771: [focaltech_moc] MOC_LIST_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.771: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-device-DEBUG: 03:39:00.771: Completing action FPI_DEVICE_ACTION_LIST in idle! 193s (process:4430): libfprint-device-DEBUG: 03:39:00.771: Not updating temperature model, device can run continuously! 193s (process:4430): libfprint-device-DEBUG: 03:39:00.771: Not updating temperature model, device can run continuously! 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.771: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.771: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.772: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.772: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.772: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.773: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.773: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.774: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.774: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.824: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.824: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.824: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.825: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.825: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.875: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.875: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.876: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.876: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.876: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.926: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.926: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.927: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.928: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 193s (process:4430): libfprint-SSM-DEBUG: 03:39:00.928: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 194s (process:4430): libfprint-SSM-DEBUG: 03:39:00.978: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 194s (process:4430): libfprint-SSM-DEBUG: 03:39:00.978: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 194s (process:4430): libfprint-SSM-DEBUG: 03:39:00.979: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 194s (process:4430): libfprint-SSM-DEBUG: 03:39:00.979: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 3 194s (process:4430): libfprint-SSM-DEBUG: 03:39:00.979: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 194s (process:4430): libfprint-SSM-DEBUG: 03:39:00.979: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 194s (process:4430): libfprint-SSM-DEBUG: 03:39:00.980: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 194s (process:4430): libfprint-SSM-DEBUG: 03:39:00.980: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 4 194s (process:4430): libfprint-SSM-DEBUG: 03:39:00.980: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 194s (process:4430): libfprint-SSM-DEBUG: 03:39:00.981: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 194s (process:4430): libfprint-SSM-DEBUG: 03:39:00.981: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 194s (process:4430): libfprint-device-DEBUG: 03:39:00.982: Device reported verify result 194s (process:4430): libfprint-device-DEBUG: 03:39:00.982: Device reported verify completion 194s (process:4430): libfprint-SSM-DEBUG: 03:39:00.982: [focaltech_moc] MOC_IDENTIFY_NUM_STATES completed successfully 194s (process:4430): libfprint-SSM-DEBUG: 03:39:00.982: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 194s (process:4430): libfprint-device-DEBUG: 03:39:00.982: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 194s (process:4430): libfprint-device-DEBUG: 03:39:00.982: Not updating temperature model, device can run continuously! 194s (process:4430): libfprint-device-DEBUG: 03:39:00.982: Not updating temperature model, device can run continuously! 194s (process:4430): libfprint-SSM-DEBUG: 03:39:00.982: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 0 194s (process:4430): libfprint-SSM-DEBUG: 03:39:00.982: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 194s (process:4430): libfprint-SSM-DEBUG: 03:39:00.983: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 194s (process:4430): libfprint-SSM-DEBUG: 03:39:00.983: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 194s (process:4430): libfprint-SSM-DEBUG: 03:39:00.983: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 194s (process:4430): libfprint-SSM-DEBUG: 03:39:00.984: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 194s (process:4430): libfprint-SSM-DEBUG: 03:39:00.984: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 194s (process:4430): libfprint-SSM-DEBUG: 03:39:00.985: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 194s (process:4430): libfprint-SSM-DEBUG: 03:39:00.985: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.035: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.035: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.035: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.036: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.036: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.086: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.086: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.087: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.087: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 3 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.087: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.088: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.088: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.089: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 4 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.089: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.089: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.090: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 194s (process:4430): libfprint-device-DEBUG: 03:39:01.090: Device reported identify result 194s (process:4430): libfprint-device-DEBUG: 03:39:01.090: Device reported identify completion 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.090: [focaltech_moc] MOC_IDENTIFY_NUM_STATES completed successfully 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.090: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 194s (process:4430): libfprint-device-DEBUG: 03:39:01.090: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 194s (process:4430): libfprint-device-DEBUG: 03:39:01.090: Not updating temperature model, device can run continuously! 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.091: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 0 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.091: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.091: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.093: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 1 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.093: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.093: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.093: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 194s (process:4430): libfprint-focaltech_moc-DEBUG: 03:39:01.094: focaltechmoc add slot: 0 194s (process:4430): libfprint-focaltech_moc-DEBUG: 03:39:01.094: FP1-00000000-0-00000000-nobody 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.094: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 2 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.094: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.094: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.095: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.096: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 3 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.096: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.097: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.097: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 194s (process:4430): libfprint-focaltech_moc-DEBUG: 03:39:01.098: delete slot 0 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.098: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 3 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.098: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 4 194s (process:4430): libfprint-device-DEBUG: 03:39:01.098: Device reported deletion completion 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.098: [focaltech_moc] MOC_DELETE_NUM_STATES completed successfully 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.098: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 194s (process:4430): libfprint-device-DEBUG: 03:39:01.098: Completing action FPI_DEVICE_ACTION_DELETE in idle! 194s (process:4430): libfprint-device-DEBUG: 03:39:01.098: Not updating temperature model, device can run continuously! 194s (process:4430): libfprint-focaltech_moc-DEBUG: 03:39:01.098: Focaltechmoc dev_exit 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.098: [focaltech_moc] DEV_EXIT_STATES entering state 0 194s (process:4430): libfprint-SSM-DEBUG: 03:39:01.098: [focaltech_moc] DEV_EXIT_STATES completed successfully 194s (process:4430): libfprint-focaltech_moc-DEBUG: 03:39:01.098: class:dc, subclass:a0, protocol:b0 194s (process:4430): libfprint-device-DEBUG: 03:39:01.098: Device reported close completion 194s (process:4430): libfprint-device-DEBUG: 03:39:01.098: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 194s (process:4430): libfprint-device-DEBUG: 03:39:01.098: Not updating temperature model, device can run continuously! 194s enrolling 194s finger status: 194s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x749b7d2fb280 (FpiDeviceFocaltechMoc at 0x20e061f0)>, 1, None, None, None) 194s finger status: 194s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x749b7d2fb280 (FpiDeviceFocaltechMoc at 0x20e061f0)>, 2, None, None, None) 194s finger status: 194s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x749b7d2fb280 (FpiDeviceFocaltechMoc at 0x20e061f0)>, 3, None, None, None) 194s finger status: 194s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x749b7d2fb280 (FpiDeviceFocaltechMoc at 0x20e061f0)>, 4, None, None, None) 194s finger status: 194s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x749b7d2fb280 (FpiDeviceFocaltechMoc at 0x20e061f0)>, 5, None, None, None) 194s finger status: 194s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x749b7d2fb280 (FpiDeviceFocaltechMoc at 0x20e061f0)>, 6, None, None, None) 194s finger status: 194s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x749b7d2fb280 (FpiDeviceFocaltechMoc at 0x20e061f0)>, 6, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 194s finger status: 194s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x749b7d2fb280 (FpiDeviceFocaltechMoc at 0x20e061f0)>, 7, None, None, None) 194s finger status: 194s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x749b7d2fb280 (FpiDeviceFocaltechMoc at 0x20e061f0)>, 8, None, None, None) 194s finger status: 194s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x749b7d2fb280 (FpiDeviceFocaltechMoc at 0x20e061f0)>, 9, None, None, None) 194s finger status: 194s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x749b7d2fb280 (FpiDeviceFocaltechMoc at 0x20e061f0)>, 10, None, None, None) 194s enroll done 194s listing 194s listing done 194s verifying 194s verify done 194s async identifying 194s indentification_done: 194s deleting 194s delete done 194s ** (umockdev-run:4426): DEBUG: 03:39:01.112: umockdev.vala:154: Removing test bed /tmp/umockdev.Q51K22 194s (umockdev-run:4426): GLib-DEBUG: 03:39:01.121: unsetenv() is not thread-safe and should not be used after threads are created 194s PASS: libfprint-2/driver-focaltech_moc.test 194s Running test: libfprint-2/driver-vfs0050.test 194s ** (umockdev-run:4438): DEBUG: 03:39:01.165: umockdev.vala:127: Created udev test bed /tmp/umockdev.ES3412 194s ** (umockdev-run:4438): DEBUG: 03:39:01.165: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 194s ** (umockdev-run:4438): DEBUG: 03:39:01.167: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 194s ** (umockdev-run:4438): DEBUG: 03:39:01.170: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.ES3412/dev/bus/usb/001/004 194s ** (umockdev-run:4438): DEBUG: 03:39:01.170: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 194s ** (umockdev-run:4438): DEBUG: 03:39:01.171: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 194s ** (umockdev-run:4438): DEBUG: 03:39:01.173: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.ES3412/dev/bus/usb/001/001 194s ** (umockdev-run:4438): DEBUG: 03:39:01.174: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 194s ** (umockdev-run:4438): DEBUG: 03:39:01.174: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 194s (umockdev-run:4438): GLib-GIO-DEBUG: 03:39:01.176: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 194s Executing: libfprint-2/driver-vfs0050.test 194s (process:4442): libfprint-context-DEBUG: 03:39:01.288: Initializing FpContext (libfprint version 1.94.8+tod1) 194s (process:4442): libfprint-tod-DEBUG: 03:39:01.289: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 194s (process:4442): libfprint-context-DEBUG: 03:39:01.291: No driver found for USB device 1D6B:0002 194s (process:4442): libfprint-device-DEBUG: 03:39:01.291: Device reported probe completion 194s (process:4442): libfprint-device-DEBUG: 03:39:01.291: Completing action FPI_DEVICE_ACTION_PROBE in idle! 194s (process:4442): libfprint-device-DEBUG: 03:39:01.291: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.292: [vfs0050] SSM_STATES entering state 0 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.293: [vfs0050] SSM_STATES entering state 1 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.293: [vfs0050] SSM_STATES entering state 2 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.294: [vfs0050] SSM_STATES entering state 3 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.294: [vfs0050] SUBSM1_STATES entering state 0 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.295: [vfs0050] SUBSM1_STATES entering state 1 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.295: [vfs0050] SUBSM1_STATES entering state 2 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.296: [vfs0050] SUBSM1_STATES completed successfully 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.296: [vfs0050] SSM_STATES entering state 4 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.296: [vfs0050] SUBSM2_STATES entering state 0 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.296: [vfs0050] SUBSM2_STATES entering state 1 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.297: [vfs0050] SUBSM2_STATES entering state 2 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.298: [vfs0050] SUBSM2_STATES entering state 3 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.298: [vfs0050] SUBSM2_STATES entering state 4 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.299: [vfs0050] SUBSM2_STATES entering state 5 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.299: [vfs0050] SUBSM2_STATES entering state 6 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.299: [vfs0050] SUBSM1_STATES entering state 0 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.301: [vfs0050] SUBSM1_STATES entering state 1 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.301: [vfs0050] SUBSM1_STATES entering state 2 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.302: [vfs0050] SUBSM1_STATES completed successfully 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.302: [vfs0050] SUBSM2_STATES completed successfully 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.302: [vfs0050] SSM_STATES entering state 5 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.302: [vfs0050] SSM_STATES completed successfully 194s (process:4442): libfprint-image_device-DEBUG: 03:39:01.302: Image device open completed 194s (process:4442): libfprint-device-DEBUG: 03:39:01.302: Device reported open completion 194s (process:4442): libfprint-device-DEBUG: 03:39:01.302: Completing action FPI_DEVICE_ACTION_OPEN in idle! 194s (process:4442): libfprint-device-DEBUG: 03:39:01.302: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 194s (process:4442): libfprint-device-DEBUG: 03:39:01.302: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 194s (process:4442): libfprint-image_device-DEBUG: 03:39:01.302: Activating image device 194s (process:4442): libfprint-image_device-DEBUG: 03:39:01.302: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.302: [vfs0050] SSM_STATES entering state 0 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.303: [vfs0050] SSM_STATES entering state 1 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.303: [vfs0050] SSM_STATES entering state 2 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.304: [vfs0050] SSM_STATES entering state 3 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.304: [vfs0050] SUBSM1_STATES entering state 0 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.304: [vfs0050] SUBSM1_STATES entering state 1 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.305: [vfs0050] SUBSM1_STATES entering state 2 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.305: [vfs0050] SUBSM1_STATES completed successfully 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.305: [vfs0050] SSM_STATES entering state 4 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.305: [vfs0050] SUBSM2_STATES entering state 0 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.306: [vfs0050] SUBSM2_STATES entering state 1 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.307: [vfs0050] SUBSM2_STATES entering state 2 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.307: [vfs0050] SUBSM2_STATES entering state 3 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.308: [vfs0050] SUBSM2_STATES entering state 4 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.308: [vfs0050] SUBSM2_STATES entering state 5 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.309: [vfs0050] SUBSM2_STATES entering state 6 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.309: [vfs0050] SUBSM1_STATES entering state 0 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.309: [vfs0050] SUBSM1_STATES entering state 1 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.310: [vfs0050] SUBSM1_STATES entering state 2 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.310: [vfs0050] SUBSM1_STATES completed successfully 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.310: [vfs0050] SUBSM2_STATES completed successfully 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.310: [vfs0050] SSM_STATES entering state 5 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.310: [vfs0050] SUBSM2_STATES entering state 0 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.311: [vfs0050] SUBSM2_STATES entering state 1 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.312: [vfs0050] SUBSM2_STATES entering state 2 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.312: [vfs0050] SUBSM2_STATES entering state 3 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.313: [vfs0050] SUBSM2_STATES entering state 4 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.313: [vfs0050] SUBSM2_STATES entering state 5 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.314: [vfs0050] SUBSM2_STATES entering state 6 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.314: [vfs0050] SUBSM2_STATES completed successfully 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.314: [vfs0050] SSM_STATES entering state 6 194s (process:4442): libfprint-image_device-DEBUG: 03:39:01.314: Image device activation completed 194s (process:4442): libfprint-image_device-DEBUG: 03:39:01.314: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 194s (process:4442): libfprint-image_device-DEBUG: 03:39:01.314: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 194s (process:4442): libfprint-device-DEBUG: 03:39:01.314: Device reported finger status change: FP_FINGER_STATUS_NEEDED 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.314: [vfs0050] SSM_STATES entering state 7 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.314: [vfs0050] SSM_STATES entering state 8 194s (process:4442): libfprint-device-DEBUG: 03:39:01.314: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 194s (process:4442): libfprint-image_device-DEBUG: 03:39:01.314: Image device reported finger status: on 194s (process:4442): libfprint-image_device-DEBUG: 03:39:01.314: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.315: [vfs0050] SSM_STATES entering state 8 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.316: [vfs0050] SSM_STATES entering state 8 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.316: [vfs0050] SSM_STATES entering state 8 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.317: [vfs0050] SSM_STATES entering state 8 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.318: [vfs0050] SSM_STATES entering state 8 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.318: [vfs0050] SSM_STATES entering state 8 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.319: [vfs0050] SSM_STATES entering state 8 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.319: [vfs0050] SSM_STATES entering state 8 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.320: [vfs0050] SSM_STATES entering state 8 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.321: [vfs0050] SSM_STATES entering state 8 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.321: [vfs0050] SSM_STATES entering state 8 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.322: [vfs0050] SSM_STATES entering state 8 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.322: [vfs0050] SSM_STATES entering state 8 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.323: [vfs0050] SSM_STATES entering state 8 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.324: [vfs0050] SSM_STATES entering state 8 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.324: [vfs0050] SSM_STATES entering state 8 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.325: [vfs0050] SSM_STATES entering state 8 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.326: [vfs0050] SSM_STATES entering state 8 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.326: [vfs0050] SSM_STATES entering state 8 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.327: [vfs0050] SSM_STATES entering state 8 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.327: [vfs0050] SSM_STATES entering state 8 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.328: [vfs0050] SSM_STATES entering state 8 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.329: [vfs0050] SSM_STATES entering state 8 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.329: [vfs0050] SSM_STATES entering state 8 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.330: [vfs0050] SSM_STATES entering state 9 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 1739677141330350 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 1 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 1 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 2 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 1 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 51 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 9 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 7 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 5 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 3 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 1 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 8 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 6 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 35 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 2 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 11 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 9 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 7 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 5 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 3 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 1 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 10 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 8 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 6 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 4 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 2 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 38 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 36 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 10 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 8 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 6 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 4 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 100 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 98 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 96 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 94 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 92 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 90 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 100 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 98 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 96 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 100 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 100 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 98 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 96 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 97 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 95 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 93 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 100 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 98 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 96 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 94 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 92 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 90 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 88 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 86 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 84 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 100 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 98 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 96 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 100 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 97 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.330: 70 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 68 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 66 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 64 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 97 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 8 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 6 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 4 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 2 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 10 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 8 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 6 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 4 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 2 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 3 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 100 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 100 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 100 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 100 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 100 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 100 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 100 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 100 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 100 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 100 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 98 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 100 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 100 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 98 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 96 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 94 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 100 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 98 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 96 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 94 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 92 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 90 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 88 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 86 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 84 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 97 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 95 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 93 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 97 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 95 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 93 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 91 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 89 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 87 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 85 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 83 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 87 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 85 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 83 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 81 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 79 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 81 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 79 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 77 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 79 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 77 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 75 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 79 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 75 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 79 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 77 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 75 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 73 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 71 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 71 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 69 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 70 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 68 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 66 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 64 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 66 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 64 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 62 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 60 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 58 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 60 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 62 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 61 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 57 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 58 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 56 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 54 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 52 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 50 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 57 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 54 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 55 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 57 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 54 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 55 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 54 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 56 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 58 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 56 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 54 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 55 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 54 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 52 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 53 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 52 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 50 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 48 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 54 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 54 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 53 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 54 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 53 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 52 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 52 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 50 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 50 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 50 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 49 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 49 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 48 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 49 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 47 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 46 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 45 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 44 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 44 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 44 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 44 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 44 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 44 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 46 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 47 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 47 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 46 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 46 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 44 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 44 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 43 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 40 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 43 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 43 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 40 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 43 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 43 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.331: 40 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 40 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 43 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 40 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 40 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 43 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 40 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 39 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 38 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 39 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 38 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 38 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 38 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 36 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 36 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 37 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 38 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 36 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 36 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 35 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 35 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 35 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 36 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 35 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 35 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 35 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 35 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 35 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 35 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 35 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.332: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 61 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.333: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.334: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.335: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.336: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.336: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.336: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.336: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.336: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.336: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.336: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.336: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.336: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.336: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.336: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.336: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.336: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.336: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.336: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.336: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.336: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.336: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.336: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.336: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.336: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.336: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.336: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.337: 1 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.337: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.337: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.337: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.337: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.337: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.337: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.337: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.337: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.337: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.337: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.337: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.337: 91 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.337: 89 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.337: 86 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.337: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.337: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.337: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.337: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.337: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.337: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.337: 60 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.337: 60 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.337: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.337: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.337: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 62 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 61 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 57 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 57 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 56 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 53 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 51 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 46 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.338: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 53 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 93 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 92 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.339: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 92 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 75 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 74 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 37 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 36 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 54 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 73 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 71 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.340: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 52 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 51 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.341: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 11 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 84 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 45 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 11 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 11 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 11 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 68 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 100 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 11 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 11 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 10 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 38 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 79 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 11 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 10 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 9 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 68 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 67 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 66 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 66 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 11 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 10 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 11 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 11 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 11 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 36 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.342: 98 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.343: 11 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.343: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.343: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.343: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.343: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.343: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.343: 9 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.343: 11 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.343: 11 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.343: 10 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.343: 10 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.343: 9 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.343: 9 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.343: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.343: 10 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.343: 10 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.343: 10 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.343: 9 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.343: 7 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.343: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.343: 10 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.343: 9 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.343: 9 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.343: 50 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.343: 61 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.343: 83 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.343: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.343: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.343: 38 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.343: 9 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 92 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 69 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 67 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 66 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 92 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 90 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 79 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 73 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 71 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 70 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 68 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 67 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 89 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 87 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 90 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 88 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 86 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 37 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 53 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 75 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 73 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 76 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 74 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 39 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 48 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 64 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 62 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 83 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 86 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 52 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 50 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 71 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 76 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 40 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 70 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 7 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 7 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 8 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 6 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 4 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 51 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 11 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 9 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 7 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 100 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 100 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 100 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 98 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 100 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 92 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 90 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 95 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 94 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 92 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 83 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 81 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 97 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 100 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 98 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 96 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 89 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 87 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 70 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 97 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 81 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 98 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 77 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 55 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 53 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 51 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 49 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 47 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 45 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 43 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 38 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 37 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 35 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.344: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 11 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 9 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 7 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 44 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 52 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 6 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 98 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 71 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 3 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 70 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 10 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 77 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 6 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 85 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 60 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 58 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 4 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 51 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 63 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 69 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 74 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 51 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 61 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 93 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 55 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 83 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 81 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 48 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 77 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 39 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 93 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 35 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 36 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 85 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 83 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 86 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 4 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 77 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 80 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 51 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 74 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 72 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 45 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 43 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 66 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 3 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 37 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 60 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 53 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 56 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 54 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 47 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 50 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 44 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 40 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 56 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 36 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 58 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 62 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 36 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 68 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 40 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 10 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 8 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 6 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 4 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 93 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 53 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 51 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 52 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 47 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 93 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 46 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 89 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 52 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 91 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 73 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 46 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 69 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 40 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 65 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 69 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 11 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 55 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 4 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 2 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 10 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 86 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 87 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 9 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 96 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 92 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 1 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 39 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 7 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 50 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 89 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 92 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 3 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 39 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 89 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 75 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 73 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 81 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 75 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 70 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 57 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 55 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 44 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 68 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 40 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 100 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 62 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 96 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 94 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 56 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 91 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 93 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 44 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 89 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 76 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 38 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 72 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 6 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 66 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.345: 3 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 55 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 83 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 49 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 5 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 3 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 6 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 4 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 38 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 37 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 98 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 81 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 88 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 88 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 89 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 11 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 9 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 75 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 3 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 71 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 80 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 67 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 76 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 74 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 52 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 79 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 77 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 97 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 40 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 1 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 45 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 84 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 5 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 68 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 83 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 81 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 74 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 1 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 75 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 73 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 66 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 69 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 67 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 65 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 61 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 57 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 9 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 53 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 51 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 100 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 1 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 96 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 95 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 6 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 88 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 86 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 5 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 93 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 75 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 81 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 9 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 77 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 67 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 73 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 69 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 50 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 67 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 65 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 63 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 84 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 40 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 95 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 55 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 53 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 65 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 84 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 65 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 45 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 39 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 58 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 35 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 11 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 63 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 54 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 49 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 9 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 9 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 7 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 5 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 1 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 36 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 37 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 5 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 3 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 8 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 1 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 4 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 7 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 10 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 7 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 6 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 4 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 2 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 6 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 1 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 2 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 6 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 4 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 2 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.346: 1 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: offsets_filtered: 1739677141348287 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 5 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 6 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 5 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 6 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 6 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 7 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 7 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 8 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 8 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 9 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 9 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 11 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 9 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 11 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.348: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.349: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.349: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.349: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.349: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.349: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.349: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.349: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.349: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.349: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.349: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.349: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.349: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.349: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.349: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.349: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.349: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.349: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.349: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.349: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.349: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.349: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.349: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.349: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.349: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.349: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.349: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.349: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.349: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.349: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.349: 90 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.349: 92 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.350: 94 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.350: 96 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.350: 96 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.350: 96 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.350: 96 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.350: 96 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.350: 96 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.350: 96 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.350: 96 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.350: 96 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.350: 96 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.350: 96 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.350: 96 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.350: 96 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.350: 96 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.350: 96 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.350: 97 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.350: 97 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.350: 97 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.350: 97 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.350: 96 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.350: 96 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.350: 96 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.350: 96 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.350: 95 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.350: 94 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.350: 93 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.350: 92 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.350: 90 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.350: 88 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.351: 86 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.351: 84 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.351: 70 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.351: 68 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.351: 68 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.351: 68 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.351: 68 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.351: 68 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.351: 68 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.351: 68 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.351: 68 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.351: 68 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.351: 68 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.351: 68 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.351: 68 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.351: 97 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.351: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.351: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.351: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.351: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.351: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.351: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.351: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.351: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.351: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.351: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.351: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.351: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.351: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 99 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 98 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 98 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 98 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 97 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 97 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 96 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 96 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 95 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 95 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 94 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 94 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 93 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 93 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 92 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 91 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 90 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 89 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 88 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 87 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 87 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 86 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 85 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 85 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 84 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 83 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 83 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 81 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 81 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 79 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 79 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 79 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 79 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 79 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 77 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 77 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 77 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 75 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 75 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 75 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 73 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.352: 71 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 71 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 70 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 69 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 68 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 66 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 66 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 64 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 64 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 62 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 62 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 61 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 60 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 60 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 58 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 58 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 57 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 57 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 57 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 57 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 56 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 56 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 56 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 55 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 55 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 55 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 54 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 54 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 54 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 54 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 54 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 54 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 54 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 54 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 54 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 54 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 54 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 53 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 53 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 53 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 52 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 52 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 52 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 52 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 50 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 50 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 50 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 50 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 49 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 49 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 49 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 49 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 48 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 47 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 47 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 47 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 46 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 46 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 46 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 46 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 45 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 44 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 44 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 44 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 44 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 44 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 44 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 44 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 44 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 43 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 43 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 43 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 43 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 43 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 40 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 40 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 40 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 39 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 39 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 38 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 38 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 38 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 38 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 38 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 37 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 36 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 36 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 36 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 36 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 36 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 35 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 35 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 35 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 35 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 35 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 35 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 35 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 35 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 35 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.353: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.354: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 30 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.355: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 19 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 18 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 16 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.356: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.357: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 11 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 11 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 11 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 11 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 11 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 11 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 11 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 11 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 11 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 11 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 10 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 10 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 10 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 10 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 10 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 10 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 10 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 10 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 10 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 10 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 10 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 10 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 12 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 38 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 50 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 61 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 66 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 67 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 67 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 68 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 69 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 70 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 70 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 70 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 71 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 71 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 73 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 73 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 73 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 73 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 73 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 73 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 73 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 73 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 73 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 71 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 70 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 70 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 68 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 67 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 67 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 64 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 64 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 62 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 53 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 53 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 52 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 52 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 50 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 48 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 40 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 40 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 40 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 40 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 40 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 40 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 40 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 40 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 51 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 51 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 81 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 83 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 90 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 92 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 92 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 92 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 92 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 92 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 92 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 94 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 94 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 94 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 94 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 92 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 92 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 90 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 89 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 87 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 83 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 81 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 81 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 77 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 70 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 55 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 53 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 51 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 49 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 47 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 45 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 43 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 38 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 37 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 35 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 20 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 24 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 51 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 51 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 58 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 58 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 58 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 58 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 60 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 60 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 60 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 61 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 61 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 61 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 61 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 55 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 55 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 60 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 53 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 53 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 54 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 53 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 53 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 51 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 51 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 51 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 51 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 51 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 50 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 47 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 50 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.358: 50 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 47 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 47 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 45 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 44 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 43 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 42 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 40 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 40 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 36 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 36 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 36 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 36 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 36 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 36 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 36 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 36 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 36 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 36 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 40 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 40 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 40 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 46 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 46 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 46 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 46 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 46 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 46 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 46 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 46 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 46 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 47 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 47 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 47 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 47 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 51 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 51 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 47 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 46 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 46 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 40 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 32 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 26 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 23 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 25 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 39 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 39 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 39 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 39 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 50 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 57 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 55 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 55 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 55 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 55 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 57 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 62 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 68 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 62 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 62 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 62 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 57 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 57 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 57 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 56 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 55 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 56 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 56 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 44 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 55 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 55 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 49 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 44 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 38 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 38 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 38 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 38 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 37 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 37 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 37 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 37 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 37 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 38 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 52 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 52 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 45 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 52 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 52 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 52 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 67 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 68 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 68 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 71 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 73 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 71 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 71 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 69 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 68 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 68 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 67 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 66 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 66 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 66 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 65 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 61 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 65 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 61 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 65 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 66 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 66 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 65 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 66 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 66 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 65 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 61 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 59 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 57 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 53 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 51 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 33 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 34 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 50 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 50 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 50 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 63 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 63 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 63 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 55 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 55 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 63 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 65 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 65 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 65 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 65 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 65 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 65 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 65 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 65 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 63 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 58 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 58 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 55 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 55 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 53 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 50 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 53 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.359: 45 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 45 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 41 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 40 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 39 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 35 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 31 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 29 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 28 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 27 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 22 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 21 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 17 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 15 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 14 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 13 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 10 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 9 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 9 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 8 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 7 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 7 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 7 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 6 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 6 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 6 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 6 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 6 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 6 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 6 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 6 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 6 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 6 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 6 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 6 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 4 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 6 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 6 194s (process:4442): libfprint-assembling-DEBUG: 03:39:01.360: 1 194s (process:4442): libfprint-image_device-DEBUG: 03:39:01.361: Image device captured an image 194s (process:4442): libfprint-image_device-DEBUG: 03:39:01.361: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 194s (process:4442): libfprint-device-DEBUG: 03:39:01.361: Device reported finger status change: FP_FINGER_STATUS_PRESENT 194s (process:4442): libfprint-device-DEBUG: 03:39:01.361: Device reported finger status change: FP_FINGER_STATUS_NONE 194s (process:4442): libfprint-image_device-DEBUG: 03:39:01.361: Image device reported finger status: off 194s (process:4442): libfprint-image_device-DEBUG: 03:39:01.361: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 194s (process:4442): libfprint-image_device-DEBUG: 03:39:01.361: Deactivating image device 194s (process:4442): libfprint-image_device-DEBUG: 03:39:01.361: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 194s (process:4442): libfprint-device-DEBUG: 03:39:01.403: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 194s (process:4442): libfprint-image-DEBUG: 03:39:01.412: Minutiae scan completed in 0.050653 secs 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.430: [vfs0050] SSM_STATES entering state 10 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.430: [vfs0050] SSM_STATES entering state 3 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.430: [vfs0050] SUBSM1_STATES entering state 0 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.431: [vfs0050] SUBSM1_STATES entering state 1 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.431: [vfs0050] SUBSM1_STATES entering state 2 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.432: [vfs0050] SUBSM1_STATES completed successfully 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.432: [vfs0050] SSM_STATES entering state 4 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.432: [vfs0050] SUBSM2_STATES entering state 0 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.432: [vfs0050] SUBSM2_STATES entering state 1 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.433: [vfs0050] SUBSM2_STATES entering state 2 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.434: [vfs0050] SUBSM2_STATES entering state 3 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.434: [vfs0050] SUBSM2_STATES entering state 4 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.435: [vfs0050] SUBSM2_STATES entering state 5 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.435: [vfs0050] SUBSM2_STATES entering state 6 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.435: [vfs0050] SUBSM1_STATES entering state 0 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.436: [vfs0050] SUBSM1_STATES entering state 1 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.436: [vfs0050] SUBSM1_STATES entering state 2 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.437: [vfs0050] SUBSM1_STATES completed successfully 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.437: [vfs0050] SUBSM2_STATES completed successfully 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.437: [vfs0050] SSM_STATES entering state 5 194s (process:4442): libfprint-SSM-DEBUG: 03:39:01.437: [vfs0050] SSM_STATES completed successfully 194s (process:4442): libfprint-image_device-DEBUG: 03:39:01.437: Image device deactivation completed 194s (process:4442): libfprint-image_device-DEBUG: 03:39:01.437: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 194s (process:4442): libfprint-device-DEBUG: 03:39:01.437: Device reported capture completion 194s (process:4442): libfprint-device-DEBUG: 03:39:01.437: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 194s (process:4442): libfprint-device-DEBUG: 03:39:01.437: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 194s (process:4442): libfprint-image_device-DEBUG: 03:39:01.438: Image device close completed 194s (process:4442): libfprint-device-DEBUG: 03:39:01.438: Device reported close completion 194s (process:4442): libfprint-device-DEBUG: 03:39:01.438: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 194s (process:4442): libfprint-device-DEBUG: 03:39:01.438: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 194s ** (umockdev-run:4438): DEBUG: 03:39:01.665: umockdev.vala:154: Removing test bed /tmp/umockdev.ES3412 194s (umockdev-run:4438): GLib-DEBUG: 03:39:01.671: unsetenv() is not thread-safe and should not be used after threads are created 194s Comparing PNGs /tmp/libfprint-umockdev-test-6wtvx747/capture.png and /usr/share/installed-tests/libfprint-2/vfs0050/capture.png 194s PASS: libfprint-2/driver-vfs0050.test 194s SUMMARY: total=36; passed=36; skipped=0; failed=0; user=26.6s; system=7.9s; maxrss=71744 195s autopkgtest [03:39:02]: test installed-tests: -----------------------] 196s autopkgtest [03:39:03]: test installed-tests: - - - - - - - - - - results - - - - - - - - - - 196s installed-tests PASS 196s autopkgtest [03:39:03]: @@@@@@@@@@@@@@@@@@@@ summary 196s installed-tests PASS 200s nova [W] Using flock in prodstack6-ppc64el 200s Creating nova instance adt-plucky-ppc64el-libfprint-20250216-033546-juju-7f2275-prod-proposed-migration-environment-20-2062f309-c473-4bde-a4f4-8ee13d9fd596 from image adt/ubuntu-plucky-ppc64el-server-20250215.img (UUID 6b0563e5-c35c-4c0f-8fb5-aae43570455f)... 200s nova [W] Timed out waiting for 61d2ea4d-2597-48e4-b324-b9ac4c8bfb90 to get deleted.